[net10.0] Update the Windows App SDK to 1.8

[MartyIX]

Description of Change

This PR builds on top of #30665 and updates to the stable version of the SDK:

• https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/stable-channel#version-18
• https://github.com/microsoft/WindowsAppSDK/releases/tag/v1.8.0

Issues Fixed

Fixes #30858

[dotnet-policy-service]

Hey there @@MartyIX! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[MartyIX]

cc @mattleibow

[PureWeen]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[jsuarezruiz]

/rebase

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[MartyIX]

1.8 was released as the stable version. Updated.

[PureWeen]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[PureWeen]

C:\Users\VssAdministrator\.nuget\packages\microsoft.windows.sdk.buildtools.msix\1.7.20250829.1\build\Microsoft.Windows.SDK.BuildTools.MSIX.Packaging.targets(3744,5): warning APPX0107: The certificate specified is not valid for signing. For more information about valid certificates, see http://go.microsoft.com/fwlink/?LinkID=241478. [D:\a\1\s\src\Controls\tests\DeviceTests\Controls.DeviceTests.csproj::TargetFramework=net10.0-windows10.0.19041.0]
  Controls.DeviceTests -> D:\a\1\s\artifacts\bin\Controls.DeviceTests\Debug\net10.0-windows10.0.19041.0\win-x64\publish\
C:\Users\VssAdministrator\.nuget\packages\microsoft.windows.sdk.buildtools.msix\1.7.20250829.1\build\Microsoft.Windows.SDK.BuildTools.MSIX.Packaging.targets(3015,5): warning : Path to `mspdbcmf.exe` could not be found. A symbols package will not be generated. Review https://aka.ms/windowsappsdkdocs and ensure that all prerequisites for Windows App SDK development have been installed. [D:\a\1\s\src\Controls\tests\DeviceTests\Controls.DeviceTests.csproj::TargetFramework=net10.0-windows10.0.19041.0]
  Controls.DeviceTests -> D:\a\1\s\src\Controls\tests\DeviceTests\AppPackages\Controls.DeviceTests_0.0.0.1_Debug_Test\Controls.DeviceTests_0.0.0.1_x64_Debug.msix
C:\Users\VssAdministrator\.nuget\packages\microsoft.windows.sdk.buildtools.msix\1.7.20250829.1\build\Microsoft.Windows.SDK.BuildTools.MSIX.Packaging.targets(3218,5): error APPX0107: The certificate specified is not valid for signing. For more information about valid certificates, see http://go.microsoft.com/fwlink/?LinkID=241478. [D:\a\1\s\src\Controls\tests\DeviceTests\Controls.DeviceTests.csproj::TargetFramework=net10.0-windows10.0.19041.0]

[MartyIX]

@PureWeen This PR targets the net10.0 branch at the moment. Is that correct? Or should it target main because it's slated for NET 9 SR12?

[MartyIX]

@PureWeen I created .NET 9 PR here: #31615

[PureWeen]

@PureWeen This PR targets the net10.0 branch at the moment. Is that correct? Or should it target main because it's slated for NET 9 SR12?

yea sorry i assigned the wrong milestone.

this should just be net10

[mattleibow]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s), but failed to run 1 pipeline(s).

[mattleibow]

@mattleibow How come I don't see the template tests error locally? I mean it passes on my machine but it failed on the CI. Now you added a few commits that appear to fix the issue. However, does the tests fail locally for you or not?

Confessions: I am not even running this, CI is my machine :)

But I am looking at the errors. The failing test is the PublishPackaged test in windows. I think they changed the path for the output msix to NOT include the RID.

AppxPackageOutput = C:\a_work_temp\test-dir\PublishPackaged1672256656\AppPackages\PublishPackaged1672256656_1.0.0.1_Test\PublishPackaged1672256656_1.0.0.1_x64.msix

[MartyIX]

@mattleibow It looks like only a few tests fail now. :)

[lothrop]

@dotMorten You were saying in #30858 all the references should point to Microsoft.WindowsAppSDK.WinUI instead of Microsoft.WindowsAppSDK?

[MartyIX]

@dotMorten You were saying in #30858 all the references should point to Microsoft.WindowsAppSDK.WinUI instead of Microsoft.WindowsAppSDK?

#31281 (comment)

[dotMorten]

@lothrop that is the recommended approach for 1.8+ class libraries. The meta data package in 1.8 is really just there for backwards compatibility until all the 3rd party libraries (including Maui) have done this work.

[mattleibow]

@MartyIX can you rebase as maybe some issues were fixed in the tests.

[MartyIX]

@MartyIX can you rebase as maybe some issues were fixed in the tests.

Done

[PureWeen]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[MartyIX]

@mattleibow Any idea what to try next?

[mattleibow]

I am doing this in a branch that is not on a fork as I think some feeds are internal or something: #32174

[rmarinho]

closing in favor of #32174