Skip to main content

.NET 7 - The type initializer for 'NUnit.Engine.Services.RuntimeFrameworkService' threw an exception

After installing .NET 7 on my development machine, the NUnit tests for some of my projects started to fail.

A look at the test logs showed the following error message:

========== Starting test discovery ==========

NUnit Adapter 4.2.0.0: Test discovery starting

Exception System.TypeInitializationException, Exception thrown discovering tests in C:\Users\bawu\source\repos\NationalRegisterNumber\NationalRegisterNumberTests\bin\Debug\net48\NationalRegisterNumber.UnitTests.dll

The type initializer for 'NUnit.Engine.Services.RuntimeFrameworkService' threw an exception.

   at NUnit.Engine.Services.RuntimeFrameworkService.ApplyImageData(TestPackage package)

   at NUnit.Engine.Services.RuntimeFrameworkService.SelectRuntimeFramework(TestPackage package)

   at NUnit.Engine.Runners.MasterTestRunner.GetEngineRunner()

   at NUnit.Engine.Runners.MasterTestRunner.Explore(TestFilter filter)

   at NUnit.VisualStudio.TestAdapter.NUnitEngine.NUnitEngineAdapter.Explore(TestFilter filter) in D:\repos\NUnit\nunit3-vs-adapter\src\NUnitTestAdapter\NUnitEngine\NUnitEngineAdapter.cs:line 88

   at NUnit.VisualStudio.TestAdapter.NUnit3TestDiscoverer.DiscoverTests(IEnumerable`1 sources, IDiscoveryContext discoveryContext, IMessageLogger messageLogger, ITestCaseDiscoverySink discoverySink) in D:\repos\NUnit\nunit3-vs-adapter\src\NUnitTestAdapter\NUnit3TestDiscoverer.cs:line 82

InnerException: System.ArgumentException: Unknown framework version 7.0

Parameter name: version

   at NUnit.Engine.RuntimeFramework.GetClrVersionForFramework(Version frameworkVersion)

   at NUnit.Engine.RuntimeFramework..ctor(RuntimeType runtime, Version version, String profile)

   at NUnit.Engine.RuntimeFramework.GetNetCoreRuntimesFromDirectoryNames(IEnumerable`1 dirNames)

   at NUnit.Engine.RuntimeFramework.FindDotNetCoreFrameworks()

   at NUnit.Engine.RuntimeFramework.get_AvailableFrameworks()

   at NUnit.Engine.Services.RuntimeFrameworkService..cctor()

NUnit Adapter 4.2.0.0: Test discovery complete

As you can see in the message above the NUnit Test Adapter doesn’t like to have .NET 7 available on my machine. This is of course a bug as the application was not even using .NET 7 (it was a .NET 4.8 application to be exact).

Luckily this was noticed by the NUnit team and they provided a fix with a 4.3 release of the NUnit Test adapter.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more