0

Before the .NET Core migration of our projects, we were using this to attach a debugger to the process so that we can debug our code: package.AddSetting(EnginePackageSettings.ProcessModel, ProcessModel.InProcess.ToString());

Now with the latest NUnit core package it seems that this process model is no longer available and debugging is attached by default. What is the best approach to deal with in process debugging toggling at this point?

We have tried the other process model options but none seem to be able to detach debugging to the process.

magicode118
  • 1,444
  • 2
  • 17
  • 26
  • I don't understand, why do you need to attach a debugger when running unit tests? Aren't you running the tests within Visual Studio (a debugger!). – Neil May 13 '20 at 10:38
  • Sorry maybe I wasn't clear and have since edited the question. We want to disable debugging and not enable it. So I'm looking for a way to detach debugger here. It seems that by default the debugger is attached to the process locally now. – magicode118 May 13 '20 at 10:40
  • If you don't want to attach a debugger, don't run the tests within Visual Studio. There are command line versions of the test runners available. – Neil May 13 '20 at 10:42
  • Yes, of course I know that, but some users find it easy to switch debug modes from VS itself and it used to work before switching to the NUnit Core version for .NET Core projects. – magicode118 May 13 '20 at 10:43

0 Answers0