7.0 Release not taking into account global.json and downgrade to 6

I have a global.json targeting 6.0.403

{ "sdk": { "version": "6.0.403", "rollForward": "latestMinor" } }

This is my donet --info

If I @System.Runtime.InteropServices.RuntimeInformation.FrameworkDescription; in my application I get:

I’m using the latest Visual Studio Mac Preview. But doing this from a command line.

Getting errors because 7 is running instead of 6.

[vitek-karas]

The DOTNET_ROLL_FORWARD explains this fully - no need for the hosting logs. The question is why is that variable set from VS Mac.

@artl93 who might be able to help with this: The short version is that in this case it seems VS Mac sets environment variable DOTNET_ROLL_FORWARD=LatestMajor for the app when it launches it. This forces the app to run on the latest available .NET runtime on the machine, which may cause problems for some apps.

[danieltharris]

@vitek-karas there’s no executable, however using dotnet bin/Debug/net6.0/appname.dll or just dotnet run from a standalone terminal works and the project is running under .NET 6 as expected.

At the start of my testing this evening after seeing your message I’ve got 4 scenarios:

1: dotnet run from standalone terminal works ✅

2: dotnet run from the VS Code integrated terminal works ✅

3: dotnet run from the VS Mac 2022 integrated terminal gives the .NET 7 related error ❌

4: run and debug from VS 2022 Mac gives the .NET 7 related error ❌

I started to dig around a bit more and I’ve found that the VS Mac 2022 Integrated terminal has the following environment variable set when I run the export command:

DOTNET_ROLL_FORWARD=LatestMajor

This is not present when executing export from either a standalone, or the VS Code integrated terminals.

If I change the env variable in the VS Mac 2022 integrated terminal with the following command:

export DOTNET_ROLL_FORWARD=LatestMinor

Then this fixes scenario 3 from the original list above…Setting it back to LatestMajor reliably breaks scenario 3 again.

This still leaves scenario 4 where debugging from VS Mac 2022 results in .NET 7 being used.

I will try to enable host tracing to see if it can help diagnose scenario 4. Not sure if DOTNET_ROLL_FORWARD is supposed to be “LatestMajor” in a standard VS 2022 Mac installation; Hopefully the above helps shed some light on what could be happening.