You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Internally, they have different names: NUnitConsoleRunnerNet60Package and NUnitConsoleRunnerNet80Package. However they use the same nuspec and contain the same files. Both are multi-targeted with Net 6.0 and 8.0 builds.
When used directly as an application, it's possible to specify either the 6.0 or 8.0 build but this doesn't work when installed as a dotnet tool. Only one implementation may be used as a command and the 6.0 version is used both cases.
NOTE: the previous release, 3.17.0 only included the .NET 6.0 implementation.
This bug will be fixed by removing one of the duplicate packages and limiting that package to the .NET 6.0 implementation as it was in the previous version. We can consider upgrading the implementation to 8.0 in a future release.
Note that users are still able to force execution under .NET 8.0 when launching the tool.
The text was updated successfully, but these errors were encountered:
Internally, they have different names: NUnitConsoleRunnerNet60Package and NUnitConsoleRunnerNet80Package. However they use the same nuspec and contain the same files. Both are multi-targeted with Net 6.0 and 8.0 builds.
When used directly as an application, it's possible to specify either the 6.0 or 8.0 build but this doesn't work when installed as a dotnet tool. Only one implementation may be used as a command and the 6.0 version is used both cases.
NOTE: the previous release, 3.17.0 only included the .NET 6.0 implementation.
This bug will be fixed by removing one of the duplicate packages and limiting that package to the .NET 6.0 implementation as it was in the previous version. We can consider upgrading the implementation to 8.0 in a future release.
Note that users are still able to force execution under .NET 8.0 when launching the tool.
The text was updated successfully, but these errors were encountered: