Hello developers,
I am working on issue
#789 of nunit-console.
To better understand the existing code I wanted to trace the control flow within the DirectoryFinder with a debugger. I wanted to use existing and new test cases as a base for this.
But somehow I can't manage to create a non-optimized build of nunit.engine and nunit.engine.api/core. So the debugger is not as helpful as I had hoped.
It doesn't matter if I build nunit by script or with Visual Studio (2019 Community). In my desperation I have already disabled the optimization for all configurations of both projects in the project files, but without success.
When I start a test via the VS test-explorer, I also see that exactly the assemblies I created before are loaded. There are no nunit assemblies in the GAC and no publisher policies.
Even though I can work without a debugger or outsource the code-to-fix to a separate project during development, I don't find either ideal.
So the questions for you experienced nunit developers are:
Do you have a setup that allows you to debug the engine?
Do you have an idea what I am doing wrong?
I checked building.md, the developer pages and the mailing list but I could not find any hints.
I'm using Windows 10 (32 Bit) with Visual Studio Community 2019 and have SDKs for .NET Framework 3.5 and Core 3.1 installed.
Thanks for your help,
Till