Migrate to Uno.Sdk and Uno Platform 7.0 - #319

Uno.Sdk 7.0.0-dev.51 / Uno.WinUI 7.0.0-dev.1656, which require .NET 10.
WinUI 2 (Uno.UI 5.x) stays on .NET 9.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E8bkzyS24p8CYDWLUPsaPC

See novotnyllc/MSBuildSdkExtras#305

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E8bkzyS24p8CYDWLUPsaPC

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E8bkzyS24p8CYDWLUPsaPC

The versions pinned by Uno.Sdk 7.0.0-dev still reference pre-7.0 Uno assemblies (unoplatform/uno#24297).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E8bkzyS24p8CYDWLUPsaPC

TextBlock has no Background in WinUI, and Uno 7 removed it for parity.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E8bkzyS24p8CYDWLUPsaPC

Uno 7 supports RichTextBlock, so the Uno WinUI 3 heads get the same ColorCode-highlighted
source viewer as Windows. ColorCode.WinUI is Windows-only, so its formatter is ported onto ColorCode.Core.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E8bkzyS24p8CYDWLUPsaPC

Uno 7 supports RichTextBlock, so the Uno WinUI 3 heads can use the Labs MarkdownTextBlock
instead of showing raw Markdown. Opt-in through LabsMarkdownTextBlockVersion until Labs
publishes a build with Uno targets. Links now open through the same handler as on Windows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E8bkzyS24p8CYDWLUPsaPC

FontWeights lives in Microsoft.UI.Text on WinUI 3, and the Labs default inline code size (10) is too small next to 14px body text.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E8bkzyS24p8CYDWLUPsaPC

Bump Uno.WinUI to 7.0.0-dev.2428 to match the Core version pinned by the SDK.
Drop the Uno.WinUI.Lottie reference: Lottie is now built into Uno.WinUI and the
standalone package stopped at 7.0.0-dev.1663, which would pull in an older Uno.WinUI.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1DnHGnhiqjJz6RnRw

3.0.3 is built against Uno.WinUI 5, so EventTriggerBehavior wasn't a WinUI 3
DependencyObject on Uno 7 (CS1503). 4.0.0-dev.10 targets Uno.WinUI 7.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1DnHGnhiqjJz6RnRw

…ects

It's part of the shared framework from .NET 10, so the explicit reference fails with
NU1510 under warnings-as-errors on the Uno 7 (net10.0) sample builds.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1DnHGnhiqjJz6RnRw

The Uno.Sdk heads referenced the published 8.2.250402 Toolkit packages, which are built
against Uno 5 and fail to compile on Uno 7 (CS0012). They now use the same logic as the
other heads: the local component projects when the repository provides them, packages otherwise.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1DnHGnhiqjJz6RnRw

…I jobs

The published Converters, SettingsControls, Extensions and Triggers packages are built
against Uno 5 and fail to compile in the Uno 7 heads (CS0012). Until Uno 7 builds are
published, the uno-linux and new-experiment (Uno.Sdk head) jobs check those components
out of CommunityToolkit/Windows at a pinned commit that ports them to Uno 7.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1DnHGnhiqjJz6RnRw

win:Background is read as an attached property by the UWP and WinAppSDK XAML
compilers (WMC0011), and the Uno TextBlock fallback has no Background.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1EDpoRrpP3hnDukwz

Uno 7 sets SupportedOSPlatformVersion to 24, which conflicts with the hardcoded
minSdkVersion 21 in the manifest (XA1036).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1EDpoRrpP3hnDukwz

The Uno.Sdk head runs on Uno 7 (Uno.WinUI). In WinUI 2 solutions it pulled the
Uno 5 Uno.UI components in next to it (UNOB0001) and built them for net10.0-ios
against net9.0-ios restore graphs (NETSDK1005).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1EDpoRrpP3hnDukwz

…aths

project-template builds the Uno.Sdk head too, so it hits the same CS0012 as the
gallery jobs with the Uno 5 Toolkit packages. Long paths are needed for the
wwwroot/package_<hash>/ files Uno's wasm runtime deploys.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1EDpoRrpP3hnDukwz

The wasdk/uwp test packages are registered by the AppX deployment service, which
can't resolve a per-user subst drive (DEP0700, AppxManifest.xml not found).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1EDpoRrpP3hnDukwz

Uno 7 moved NativeApplication and ApplicationActivity to Uno.UI.Runtime.Android
(CS0234), and NativeApplication now builds the app through CreateHost.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1EDpoRrpP3hnDukwz

On WinUI 3 macos maps to the shared net10.0 build, but only wasm/wpf/win32/linux
marked that build as Uno. A component targeting macos without those got a bare
net10.0 build with no WinUI references or constants (CS0246 on Windows.UI.Xaml).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1EDpoRrpP3hnDukwz

On WinUI 2 macos is Mac Catalyst, but it also enabled the shared net9.0 build,
which a component targeting macos without wasm/wpf/linux got as a bare net9.0
library with no Uno or WinUI references (CS0246 on Windows.UI.Xaml).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1EDpoRrpP3hnDukwz

Picks up unoplatform/uno#25841, which drops [DynamicallyAccessedMembers] from
DependencyProperty.Register.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1EDpoRrpP3hnDukwz

Building the Uno.Sdk head one TFM at a time let a later successful build overwrite $LASTEXITCODE, so CI passed with a failed desktop build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1X7Zewxqb59NXx6g8

Mirrors GenerateAllSolution.ps1: WinUI 2 with wasm plus an Uno.Sdk MultiTarget dropped the classic Wasm head for the Uno 7 head.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1X7Zewxqb59NXx6g8

dotnet run can't pick a framework of a multi-targeted project on its own.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1X7Zewxqb59NXx6g8

They skip App.Head.props' AddAssemblyAttributes, so the docs renderer hid its Source code / Package info panel.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXMNu1X7Zewxqb59NXx6g8