-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add support for net standard #12
Comments
@ChrisMaddock Can addins target .NET Standard yet? |
@jnm2 Not to be overly picky, but they are called "Engine Extensions". The term "Addins" is used in NUnit in two ways: (1) a now-obsolete method of extending the v2 framework and (2) a proposed enhancement to engine extensions, which bundles extensions targeting multiple points and possibly multiple applications (e.g. engine and gui) into the same assembly. In anticipation of implementing the second, I used The desire for users to have the same extensions available in the .NET Standard "engines" is very natural and is one of the main reasons I thought that calling them "engines" was a bad idea. |
@JMM2, not yet unfortunately. There’s an updated .NET standard engine on a branch at the moment. Extensions are a little further down the list. 😊 |
Oh, right. That makes sense. Can we link this issue so we don't lose track of it? |
At the moment, the only source of this discussion is here: https://github.com/orgs/nunit/teams/engine-team/discussions/4 Turning that discussion into publicly visible issues is still on my todo list. 😞 |
Moving this out of the 3.7 milestone while we discuss whether to support V2 output in dotnet core. |
The 3.8.0 release of this extension will have extension assemblies targeting .NET 4.6.2 and .NET 6.0. Do we also need a .NET Standard build, given that you can readily test .NET Standard libraries using .NET 6.0? |
Closing this since we now support .NET Standard 6.0. |
I am currently calling running NUnit tests in a .NET Standard 2.0 project using the nunit.engine.netstandard NuGet package.
After running the tests, I would like to generate the NUnit2 xml report to pass it on to Specflow's report generator. Presently, NUnit.Extension.NUnitV2ResultWriter target .NET Framework so I cannot initialize the NUnit2XmlResultWriter and call the WriteResultFile() in my .NET Standard project.
The text was updated successfully, but these errors were encountered: