Closed madelson closed 1 year ago
Thanks for raising this @madelson I'm not heavily involved with the adapter project but I suspect this may already be tracked under https://github.com/nunit/nunit3-vs-adapter/issues/1049. Luckily, that issue is slated for the next milestone which means this should be fixed with the next minor release. Sorry, but based on what @OsirisTerje has mentioned there you may need to uninstall .NET8 in the meantime to be able to use the adapter. Alternately, if it's an option for you in the interim, I believe 3.16.2 is the latest release of the console runner and should be using version 3.16.2 of the engine which may work for you.
I'm going to close this as a duplicate, but note that we will be able to see any follow-up questions or comments.
Thanks @stevenaw . I'll watch that issue.
@madelson Version 4.4.0-beta.1 is out now https://www.nuget.org/packages/NUnit3TestAdapter/4.4.0-beta.1 . It includes support for .net 8.
It contains the engine version 3.16.3. Appreciate it if you have the time to verify it works as it should.
Once verification is done, the non-beta will be published.
Thanks @OsirisTerje . I just installed it and it works like a charm!
I installed .NET 8 preview and my NUnit .NET framework tests now fail with this issue, but for .NET 8:
While this PR comment says that this should be fixed in Engine 3.16, The docs say that the latest adapter only brings in engine 3.15.2. Could we have a new adapter release which embeds engine 3.16 to fix this?