Invalid assemblies no longer give an error message
See original GitHub issueIn the NUnit3 console runner 3.7, the argument x.dll
gives an error message indicating the file was not found. Typing x.junk
gives a message saying that the file type is not known.
In the current master build, the run fails without specifying a message in both cases.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Invalid assembly error when calling WCF service with EF
When loading assemblies CLR first looks in GAC and ignores whatever you have in your bin directory. If you don't have the .NET...
Read more >Troubleshoot .NET Framework targeting errors
To resolve the error, make sure that your application targets a .NET version that's compatible with the version that's targeted by the projects ......
Read more >Error: "Tasks not processed because the script assemblies ...
When looking at the system journal the following warnings are displayed: "Tasks not processed because the script assemblies are not valid."
Read more >Visual studio 2019 16.0.2. The reference is invalid or ...
When i open my project with vs19 16.0.2 and try to add dll references it gives me an error which says : “The...
Read more >C# Build Error - Missing Reference Assemblies for .Net4
The reference assemblies for .NETFramework,Version=v4.0 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
UPDATE: This turns out to not be an issue, since we only display ignored test cases.
Hmmm… looking at the framework, I am suspicious that we may have a similar problem with ignored tests as we have with warnings… the suite containing the ignored test getsResultState.Ignored
andFailureSite.Child
is not specified. I’ll run a test to see and update this PR if necessary.I was waiting for travis to pass before doing the PR on this one, but I guess I’ll stop doing that. 😄
In practice, the framework fix should be looked at before the console fix, so we don’t have to fix the console twice. I’ll move to that next.