Clarify RID catalog casing #30141
Description
Clarify RID catalog casing
Developers sometimes need to compute RIDs programmatically, e.g. a custom publishing wizard in Visual Studio that can only rely information like the solution configuration manager and project properties. If the solution configuration passes invalid value, e.g. ARM64 instead of arm64, you end up with a potentially invalid RID like win-ARM64.
We should clarify that computed RIDs must match the catalog. RIDs with different casing would also cause problems when the OS is case sensitive, like Linux, as the value is often used when constructing output paths, etc.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 009616d0-6c93-a2de-82fe-4f7168817f18
- Version Independent ID: 4c2c5549-0151-516d-91d0-9b017c74e787
- Content: .NET Runtime Identifier (RID) catalog
- Content Source: docs/core/rid-catalog.md
- Product: dotnet-fundamentals
- GitHub Login: @tdykstra
- Microsoft Alias: dotnetcontent