CharliePoole

@SimonCropp `TestAssemblyResolver`, sets the `Resolving` event of the load context to `OnResolving` in its constructor. Someone with in-depth knowledge of SqlClient will probably need to look at this.

I'm guessing that's because it's in the base directory, but I'm really not sure. Can you see what happens if you remove it at execution time?

@Lorilatschki Did this process work before you upgraded to 3.16? This may be related to #1275.

The logs should all be found in the same directory. The agent could simply be failing before it creates the named log. Does the log appear when there is no...

@Lorilatschki Best best would be for you to create a non-intermittent repro, if possible. There seems to be an associated issue here as well: the main log tells you to...

@goldcode The link to your example project doesn't work, so I'm not able to see what you specifically added to the project file in order to make it work. Also,...

The NUnit.ConsoleRunner nuget package runner uses .NET Framework 4.6.2 (in 3.16) but launches a process for your .NET 6.0 executable. The NUnit.ConsoleRunner.NetCore package has a runner with fewer options, which...

I have run a simple test targeting netstandard2.0 and 2.1, with no further changes to the engine code. The test did no more than Assert.Pass() so we would want to...

One small advantage of allowing it is that we don't have to make special provision for handling it in the code as we now do. It's not much, however, and...

Regarding running under Visual Studio, I think that's not a problem because AFAIK VS never passes a .NET Standard assembly to be executed. @OsirisTerje is that correct? I don't know...