microsoft / TemplateStudio

Template Studio accelerates the creation of new WinUI 3, WPF, and UWP apps using a wizard-based experience.
Other
2.65k stars 459 forks source link

[WIP] change RuntimeIdentifier to win-xxx for .NET 8.0 -- fix issue #4717 #4723

Open tonymet opened 6 months ago

tonymet commented 6 months ago

PR checklist

Quick summary of changes Fix .NET 8.0 specified RuntimeIdentifier 'win10-x64' is not recognized.

Full Error

NETSDK1083  The specified RuntimeIdentifier 'win10-x64' is not recognized. See https://aka.ms/netsdk1083 for more information.

More info: https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/8.0/runtimeidentifier

Steps to Repeat

  1. Create new project from template
  2. Build Project

Which issue does this PR relate to?

4717

Applies to the following platforms

Anything that requires particular review or attention?

Do all automated tests pass?

✅ yes

Have automated tests been added for new features? N/A

If you've changed the UI: n/a

If you've included a new template: n/a

Have you raised issues for any needed follow-on work? n/a

Have docs been updated? no

If breaking changes or different ways of doing things have been introduced, have they been communicated widely?

licon4812 commented 6 months ago

I was able to get this working locally by adding this to my csproj

<UseRidGraph>true</UseRidGraph>
<RuntimeIdentifiers>win10-x86;win10-x64;win10-arm64</RuntimeIdentifiers>
pratikone commented 3 months ago

Thahks for this. @licon4812 is correct. I am planning to use true for maximum backward compatibility for the next release. You can close this PR or change to use Rid

tonymet commented 3 months ago

can you clarify? has it been fixed?

pratikone commented 3 months ago

not yet. I am suggesting to use <UseRidGraph>true</UseRidGraph> in your PR instead of win-x64 values so that it is backward compatible and then lets merge it UseRidGraph>true</UseRidGraph> <RuntimeIdentifiers>win10-x86;win10-x64;win10-arm64</RuntimeIdentifiers>