Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/nunit/nunit-console/issues/1467 below:

Console output is unclear about which console build is running · Issue #1467 · nunit/nunit-console · GitHub

We have three different builds of the console runner, all producing the executable nunit3-console.exe:

1. The "standard" console built with .NET Framework 4.6.2, which has full functionality.
2. The "netcore" runner built with .NET Core 6.0, with limited functionality.
3. A second "netcore" runner, with the same limited functionality, built against .NET Core 8.0.

Often, users don't actually remember which console they installed, resulting in a lot of confusion both for them and for the team when bugs are reported. For example, if the user says they are using .NET 6.0, that may mean they are using either the standard runner with a .NET6.0 agent or the .NET 6.0 runner or even the .NET 8.0 runner!

Ideally, we should not have three different programs with the same name. However, changing the executable name is a breaking change and will need to be postponed until the 4.0 release.

To mitigate the problem, the initial header in the console output should clearly state which of the three is being run. We might even consider a one-line notice like "Bugs should be reported against XXX."

It might also be useful to have a page somewhere, which describes the limitations of the .NET Core builds.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4