CharliePoole

@rcocks-hl Seems that I lost track of this issue but fixed another one, which describes the same problem, #1182. It's in the 3.16 release, which just came out a few...

This is likely to be a problem with the Visual Studio project loader extension. What version of it are you using with NUnit-console? In addition, you should try removing the...

@rameshkadev I'm confirming that this is a bug in both the engine and the project loader. Running your .NET Standard main assembly directly or via the `.csproj` file gives the...

Thinking about this, I wondered why we can't allow running tests, which target .NET Standard, which has been a stated limitation ever since we began to support .NET Core. The...

This issue has been resolved in version 3.16.0 The release is available on: [GitHub](https://github.com/nunit/nunit-console/releases/tag/3.16.0). NuGet packages are also available [NuGet.org](https://www.nuget.org) and Chocolatey Packages may be found at [Chocolatey.org](https://chocolatey.org)

@OsirisTerje It's not clear from the repo project how the console runner gets into your netcoreapp3.1 directory. How is it installed?

But you're typing `nunit3-console Issue912.dll` in that directory. So I was wondering if you used the chocolatey package, the msi, or what? AFAIR only chocolatey sets up an alias.

OK... I'll install the same way and check it out.

I first installed using chocolatey (because it's so much easier) and was able to run without error. I next uninstalled the chocolatey package and installed the msi. I added the...

@OsirisTerje ~~You could also try deleting addins from your install, if you are not using them.~~ DIDN'T WORK!