-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting a TypeInitializationException after upgrading to NUnit Console Runner 3.16.0 and NUnit 3.13.3. #1280
Comments
As an experiment, can you install .NET 4.6.2 and try to run? |
I encountered the same time error message. Below are my versions: installed in project: nunit.consolerunner = 3.16.0 Update 1: I installed the .netcore 6 SDK on the target machine and it worked |
Ran the installer for .NET 4.6.2, but it completed rather quickly. Maybe because .NET 4.8 is already installed. Anyhow, after running the .NET 4.6.2 installer and trying the console runner again I still get the same error. BTW..., I ran a PS query to list .NET versions and here is what I got:
|
Having the same issue on a Windows 10 TeamCity VM (it works fine on my local Windows 10 VM which has exact same versions installed). CLR version:
Log output:
|
What dotnet runtimes are installed? |
dotnet command doesn't exist on the target machine in my environment, likely because .Net core is not installed. Only .Net 4.6.1 SDK and .Net 4.8 Framework are installed. |
In that case, this is a duplicate of #1277, which was closed. The fix is available from our MyGet feed as version 3.16.1-dev00006 |
This is occurring on a Windows 7 system that has .NET 4.6.1. The installation of NUnit components was done via Nuget within Visual Studio 2022. The NUnit test project was compiled targeting .NET 4.6.1.
Note that the Console Runner is able to run on the system where I have VS 2022 installed. However, it will not run on the test agent that doesn't have VS 2022 installed even though it used to run on that agent with Console Runner 3.14.0. Note that the test agent has .NET 4.8 installed on it in addition to .NET 4.6.1.
Behavior is no different when running with --inprocess.
The text was updated successfully, but these errors were encountered: