NETSDK1206 error for aspnetcore repo in stage 2 bootstrapping build leg

[mthalman]

/vmr/.dotnet/sdk/8.0.100-preview.6.23315.1/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.targets(267,5): error NETSDK1206: Found version-specific or distribution-specific runtime identifier(s): win. Affected libraries: System.Security.Cryptography.Pkcs. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details. [/vmr/src/aspnetcore/artifacts/source-build/self/src/src/DataProtection/DataProtection/src/Microsoft.AspNetCore.DataProtection.csproj::TargetFramework=net8.0]

Example build (internal link)

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[mthalman]

Logged aspnetcore issue for this: dotnet/sdk#33486

[mthalman]

Reopening as this issue doesn't seem to be resolved by dotnet/installer#16699.

[mthalman]

What's interesting about the fix in dotnet/installer#16699 is that it partially resolves the issue. Originally, these projects had the error:

Microsoft.AspNetCore.DataProtection.csproj
Microsoft.AspNetCore.DataProtection.Extensions.csproj
Microsoft.AspNetCore.Hosting.csproj
Microsoft.AspNetCore.Session.csproj
Microsoft.AspNetCore.Antiforgery.csproj
Microsoft.AspNetCore.Server.HttpSys.csproj
Microsoft.AspNetCore.Server.IIS.csproj
Microsoft.AspNetCore.Server.Kestrel.csproj
Microsoft.AspNetCore.Authentication.csproj
Microsoft.AspNetCore.csproj
Microsoft.AspNetCore.Authentication.BearerToken.csproj
Microsoft.AspNetCore.Authentication.OAuth.csproj
Microsoft.AspNetCore.Authentication.Cookies.csproj
Microsoft.AspNetCore.Identity.csproj
Microsoft.AspNetCore.Components.Endpoints.csproj
Microsoft.AspNetCore.Components.Server.csproj
Microsoft.AspNetCore.Mvc.ViewFeatures.csproj
Microsoft.AspNetCore.Mvc.Razor.csproj
Microsoft.AspNetCore.Mvc.RazorPages.csproj

After applying that fix, then it seems there is unpredictable behavior because, typically, one or two of these projects will still fail with the error in a build. Sometimes, it all passes. It's all sporadic.