[SARIF Multitool] Allow running as tool on a non-EOL version of .NET Runtime (.NET Core 3.1 support ended in December 2022)

[KalleOlaviNiemitalo]

The Sarif.Multitool package targets netcoreapp3.1 and net472. I tried to use it as a .NET tool on a computer that had Windows and .NET SDK 6.0.302 but no .NET Core 3.1 runtime. dotnet tool install installed it okay, but dotnet tool run sarif failed to launch and told me it needs the .NET Core 3.1 runtime. Because Microsoft will stop supporting .NET Core 3.1 on December 13, 2022, I'd like to start uninstalling its runtime from computers.

Could you change the Sarif.Multitool package so that it will work on .NET 6.0 without needing the .NET Core 3.1 runtime? Perhaps by multitargeting, or perhaps by configuring roll-forward.

(The Sarif.Multitool.Library package has no such problem, because it targets netstandard2.1 and net472.)

[KalleOlaviNiemitalo]

I can apparently override this by setting DOTNET_ROLL_FORWARD=Major in the environment. That feels a bit suspicious though, because if the tool started any child processes, they too would inherit the environment variable.

[KalleOlaviNiemitalo]

dotnet/sdk#26417 (comment) seems to recommend that .NET tool packages allow major version roll-forward.

[KalleOlaviNiemitalo]

.NET Core 3.1 support has now ended.

[KalleOlaviNiemitalo]

.NET SDK 8.0.300 supports dotnet tool install --allow-roll-forward, implemented in dotnet/sdk#37231. For local tools, it writes "rollForward": true into the .config/dotnet-tools.json file.

[KalleOlaviNiemitalo]

Fixed in #2864, released in https://github.com/microsoft/sarif-sdk/releases/tag/v4.6.0