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
Right now VSTest will run .NET Framework assemblies using Mono on Unix platforms. This was useful in the past but nowadays the more common usage is multi-targetting a test assembly for net462/net8 where the netfx assembly contains Windows-specific code.
This results in issues like dotnet/runtime#81395 where a test assembly tried to run on mono unexpectedly.
Steps to reproduce
$ dotnet new mstest
Edit the .csproj to contain <TargetFrameworks>net462;net8.0</TargetFrameworks> and <LangVersion>Latest</LangVersion>.
Run dotnet test
Expected behavior
Only runs the tests once, for the net8.0 assembly.
Actual behavior
Runs both the net8.0 and net462 assembly, the latter using Mono.
Diagnostic logs
Environment
macOS 14, dotnet 8
The text was updated successfully, but these errors were encountered:
I see how that would be useful, it would have to be a new flag, to avoid breaking people who are relying on the current behavior. We could add it to dotnet test msbuild task, so you could put opt-out flag directly into your project (e.g. false). And as a new runconfiguration.
Description
Right now VSTest will run .NET Framework assemblies using Mono on Unix platforms. This was useful in the past but nowadays the more common usage is multi-targetting a test assembly for net462/net8 where the netfx assembly contains Windows-specific code.
This results in issues like dotnet/runtime#81395 where a test assembly tried to run on mono unexpectedly.
Steps to reproduce
Edit the .csproj to contain
<TargetFrameworks>net462;net8.0</TargetFrameworks>
and<LangVersion>Latest</LangVersion>
.Run
dotnet test
Expected behavior
Only runs the tests once, for the
net8.0
assembly.Actual behavior
Runs both the
net8.0
andnet462
assembly, the latter using Mono.Diagnostic logs
Environment
macOS 14, dotnet 8
The text was updated successfully, but these errors were encountered: