CharliePoole

The metadata is a build dependency but the dll is bundled with the package. We might want to change that.

TC Metadata version 2 has breaking changes, so if somebody (I think before me) updated 3.17 to use it they may not have correctly updated how they are doing it....

@PatrickLeGarrec It seems to me that the Load or LoadFrom ought to work as well, provided that we correctly handle any "Unloading" events. Also, I'd like to compare the handling...

So, after all this... what in your opinion is the minimum code needed to demonstrate the error? Load + Unload + Check for file locked? We could do that for...

I created unit tests, which demonstrate that the assembly files are locked when loaded and stay locked after unload. This is actually consistent for both .NET Framework and .NET Core...

Separate problems exist for .NET Framework and .NET Core. In the .NET Framework case, we unload the test by unloading the AppDomain. This made sense in the early years of...

The division into two "phases" in the life-cycle of a test is intrinsic to NUnit and is the cause of a lot of problems for users. On the custom attribute...

@KJoreth Is this still a current problem for you? If so... Have you tried using 3.18.2? Which build of nunit3-console are you using? i.e. .NET Framework, .Net 6.0, .NET 8.0?

@stevenaw Not only those. Default names of parameterized tests include the args provided by the user. It can occur in either a string or a char arg or any compound...

I got curious as to why we added the exception thrown when the class is not resolvable. Turns out to have been introduced in the second commit in the present...