.NET11+ on windows runner w/o system installed .NET11.0* SDK #729

Usage Information

Fallout 10.5.0-rc.3 / 11.0.100-rc.2* / .NET11.0 / Win11

Description

Fallout now runs well with .NET11.. so far so good

One little thing maybe even fixed for Fallout 10.5.0 is following:

When running on a windows host w/o installed .NET11.0 SDK, the build.ps1 bootstrapper attempts to download the SDK. That works, but uncompressing fails, because dotnet-install.ps1 prefers .tar.gz (even on windows). The windows version of tar cannot uncompress this because of:

dotnet-install: Remote file https://builds.dotnet.microsoft.com/dotnet/Sdk/11.0.100-rc.2.26504.105/dotnet-sdk-11.0.100-rc.2.26504.105-win-x64.tar.gz size is 257143022 bytes.
dotnet-install: Downloaded file https://builds.dotnet.microsoft.com/dotnet/Sdk/11.0.100-rc.2.26504.105/dotnet-sdk-11.0.100-rc.2.26504.105-win-x64.tar.gz size is 257143022 bytes.
dotnet-install: The remote and local file sizes are equal.
dotnet-install: Extracting the archive.
dotnet-install: Failed to extract tar package. Exception: ./: Cannot extract through symlink \\\\?\\C:\\GitLabRunner: too many symbolic link levels
tar.exe : ./: Cannot extract through symlink \\\\?\\C:\\GitLabRunner: too many symbolic link levels

Reproduction Steps

• Move solution to latest .NET11.0-rc version
• Update build to .net11.0
• run pipeline on a windows runner with no previous SDK setup
• see this error

Expected Behavior

Should work

Actual Behavior

Fails the decompress step of SDK setup

Regression?

No

Known Workarounds

No workaround but the windows fix is (using the old behavior of <11):

Add this to the build.ps1:

$env:DOTNET_INSTALL_SKIP_TAR = "1"

This works and falls back to .zip again.

Could you help with a pull-request?

Yes