Description

I encountered the following error while building my project using the .NET 9.0 SDK:

C:\Program Files\dotnet\sdk\9.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(90,5): Error NETSDK1083: The specified RuntimeIdentifier 'win10-x86' is not recognized. See https://aka.ms/netsdk1083 for more information.

Questions:

1. Is win10-x86 a valid RuntimeIdentifier for .NET 9.0? If not, what should I use instead?
2. Is there a compatibility issue between targeting net8.0 and using the .NET 9.0 SDK?
3. Are there additional steps I should take to resolve this issue?
   Any help or guidance would be appreciated!

Steps to Reproduce

1. SDK Version:
   .NET SDK 9.0.100 (verified using dotnet --list-sdks)

2. Target Framework:
   net8.0 (because i am using Evergine:

3. Project File (.csproj):
   Here is a simplified version of my .csproj file:

<PropertyGroup>
    <TargetFramework>Condition="$([MSBuild]::IsOSPlatform('windows'))">$(TargetFrameworks);net8.0-windows10.0.19041.0</TargetFramework>
    <RuntimeIdentifier>win10-x86</RuntimeIdentifier>
</PropertyGroup>

Development Environment:

OS: Windows 11 Home 64-bit (10.0, Build 22632)
IDE: Microsoft Visual Studio Community 2022 (64-bit) - Current
Version 17.12.1

Link to public reproduction project repository

No response

Version with bug

9.0.10 SR1

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

Windows

Affected platform versions

net8.0-windows10.0.19041.0

Did you find any workaround?

1. Changed RuntimeIdentifier to win-x86 or win-x64, but the same issue persists.
2. Verified the .NET SDK installation (dotnet --list-sdks confirms the correct version is installed
3. Ran dotnet clean and dotnet restore before rebuilding.
4. have tried to instal workload with command: dotnet workload install maui
   
5. have adding <UseRidGraph>true</UseRidGraph>
6. have download
7. Followed the discussion in this GitHub issue comment to check for potential workarounds, but the error persists in my case.

Relevant log output