Delete the non portable RID graph in a future release of .NET

[ViktorHofer]

Follow-up on dotnet/sdk#34279, see discussion in #92211

[ghost]

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Follow-up on dotnet/sdk#34279

Author:	ViktorHofer
Assignees:	ViktorHofer
Labels:	area-Infrastructure-libraries, blocking-release
Milestone:	8.0.0

[ViktorHofer]

cc @tmds @MichaelSimons @dsplaisted

[dsplaisted]

Do we want to delete this entirely? The SDK still consumes and includes the old runtime graph from dotnet/runtime, and projects can opt in to using it by setting UseRidGraph to true.

[ViktorHofer]

We don't want anyone to mutate the current runtime.json RID graph anymore. It's de-facto frozen. I was under the impression that the full RID graph already moved to the SDK with your recent change. I think we should do that.

[dsplaisted]

No, so far only the trimmed-down, portable graph has been moved to the SDK. The full RID graph still comes from runtime.

[ViktorHofer]

I see, thanks for the clarification. Any objection to moving it over? We don't want to ship new versions of Microsoft.NetCore.Platforms anymore, nor do we want to have a transport package, only to carry over a checked-in, frozen asset to the sdk repository.

[ViktorHofer]

gentle ping @dsplaisted. Whatever we do, we should do it asap as the cut-off for RC1 is approaching. Would you mind adding the full RID graph into the sdk repository and removing the dependency on Microsoft.NETCore.Platforms?

[dsplaisted]

I would prefer to wait until .NET 9 to make the changes to runtime if that's OK. The RID changes are coming in kind of late for .NET 8, and I'd prefer to avoid extra churn. This shouldn't affect any runtime or SDK behavior, right, it's just about simplifying the runtime build?

[ViktorHofer]

We want to stop shipping the Microsoft.NETCore.Platforms package to make it clear that the graph is frozen. The package today appears on nuget.org. While we could just make it a transport package for the current release, I wonder if it wouldn't be easier to just move the graph into the sdk repo. I'm fine with either option for .NET 8.

[dsplaisted]

I would prefer for .NET 8 to just mark it as a transport package, and then remove it for .NET 9.