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

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more