Re-Bootstrap Source Build to .NET 10.0.100-alpha.1.24556.1

[dotnet-sb-bot]

Re-Bootstrap Source Build to .NET 10.0.100-alpha.1.24556.1

Fixes dotnet/source-build#4720

[ViktorHofer]

Can we re-bootstrap to a newer Arcade.Sdk? I see this points to https://github.com/dotnet/arcade/tree/1818ed2babf890a1cd62fa96a1f03abdada2d003. It would be great if we could have dotnet/arcade@e0270d6 included (or ideally main HEAD).

Asking as that newer commit will allow fixing dotnet/source-build#4719

[ViktorHofer]

@mthalman I pushed into your branch as I noticed that we don't consistently set NetCurrent to net10.0. We only set it for a set of projects (which don't import Arcade). That was overlooked in the previous net10.0 TFM PR. Hope that's OK.

[MichaelSimons]

Can we re-bootstrap to a newer Arcade.Sdk?

We really shouldn't. The arcade, SDK, and previous SB artifacts should all be from the same build. Deviating from this often leads to prebuilts and other possible breaks. I would rather we just rebootstrap again once a build is available with the arcade fix. We have automation for this now so it can be as simple as queuing a build.

[ViktorHofer]

Isn't a build with the Arcade fix already available? Oh I just noticed that the full source-build pipeline only runs once per day. Understood.

[mthalman]

@mthalman I pushed into your branch as I noticed that we don't consistently set NetCurrent to net10.0. We only set it for a set of projects (which don't import Arcade). That was overlooked in the previous net10.0 TFM PR. Hope that's OK.

Ah, so that probably explains why dotnet/source-build#4720 is happening.

[mthalman]

Arcade is failing to build in sdk-source-build:

/vmr/src/arcade/src/Microsoft.DotNet.Build.Tasks.Workloads/src/Microsoft.DotNet.Build.Tasks.Workloads.csproj error NU1202: Package Microsoft.NET.Sdk.WorkloadManifestReader 10.0.100-alpha.1.24556.1 is not compatible with net9.0 (.NETCoreApp,Version=v9.0). Package Microsoft.NET.Sdk.WorkloadManifestReader 10.0.100-alpha.1.24556.1 supports: net10.0 (.NETCoreApp,Version=v10.0) [/vmr/src/arcade/Arcade.sln]

Looks like we'll need the fix at dotnet/arcade@e0270d6. I'll get a full run of source build with this fix that we can use to bootstrap with.

[ViktorHofer]

This one is different. Arcade consumes an sdk package but sdk already updated their TFM to net10.0. Arcade is still on net9.0.

[mthalman]

This one is different. Arcade consumes an sdk package but sdk already updated their TFM to net10.0. Arcade is still on net9.0.

Ah. Do you know of any blockers to getting it on net10.0?

[ViktorHofer]

Nope. The blocker got fixed yesterday with the net10.0 PR merged.

[mthalman]

I'll probably create a patch for this. I know there's been pushback in the past about arcade upgrading to a new TFM too early.

[ViktorHofer]

Here's the Arcade PR: dotnet/arcade#15221. Feel free to create a patch from it.

[ViktorHofer]

You probably also need the latest commit from dotnet/arcade#15221. That was an unintentional change that I fixed with it.

[mthalman]

Source build error in nuget-client:

/vmr/src/nuget-client/src/NuGet.Core/NuGet.Packaging/Signing/Utility/CertificateChainUtility.cs(131,27): error CS0433: The type 'X509CertificateLoader' exists in both 'Microsoft.Bcl.Cryptography, Version=10.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' and 'System.Security.Cryptography, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' [/vmr/src/nuget-client/src/NuGet.Core/NuGet.Packaging/NuGet.Packaging.csproj]

This is the same issue that was identified in #44540.

[am11]

Looks like we may need another change similar to NuGet/NuGet.Client#5911? cc @akoeplinger

[mthalman]

I added a patch to update nuget-client to net10.0 which should resolve the X509CertificateLoader issue there.

[ViktorHofer]

Is the plan with this PR to patch all VMR repositories to target net10.0?