Skip to content

[Temporary, do not merge] PR build on .NET 10 - #22

Closed
turbobobbytraykov wants to merge 8 commits into
vnextfrom
tmp/pr-build-on-dotnet-10
Closed

turbobobbytraykov wants to merge 8 commits into
vnextfrom
tmp/pr-build-on-dotnet-10

Conversation

@turbobobbytraykov

Copy link
Copy Markdown
Contributor

Temporary draft: #18 (.NET 10) merged with #20 (PR build and the iOS/Mac Catalyst platform files), only to run the platform matrix on .NET 10 before either is merged. I'll close it and delete its branch when the run finishes.

🤖 Generated with Claude Code

turbobobbytraykov and others added 8 commits November 11, 2026 08:38
.NET 9 support ended on 2026-11-10. global.json now pins the 10.0.1xx SDK band
(10.0.100, latestPatch), which Visual Studio 2022 17.14 can still load, and every
project targets net10.0: the samples browser, the 331 standalone samples, the
sample template and the two CI helper tools. The HintPaths to the dev-tools
build output keep net9.0, the libraries' own framework.

On net10.0-desktop, Uno 6.7 adds the WebView2Aot package, whose WebView2 namespace
hid the WebView2 control in SampleHostPage; the type is now fully qualified.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The retiring service worker, the Open Sans subset and the gzip removal were
conditioned on net9.0-browserwasm, so .NET 10 would have skipped them (and their
CI checks would have failed the build). Their comments now name the .NET 10
bootstrapper and SDK too: both still write service-worker.js and .gz copies.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PR build (pr-build.yml) runs on pull requests to vnext and main and deploys
nothing. It calls the build job of build-and-deploy.yml as a reusable workflow,
so a PR is checked with the same AOT publish and site validation that deploys,
and its dispatch job is skipped. A matrix then builds the samples browser for
android and desktop, and three samples (plus up to five the PR changes) for
android, desktop, browserwasm, ios and maccatalyst. The target framework is read
from SamplesBrowser.csproj, so the matrix follows a framework change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first run showed that the standalone samples list ios and maccatalyst but cannot build them: they have no Platforms/iOS or Platforms/MacCatalyst files (Info.plist is missing). The workflow comment says what to add before putting those platforms back.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review follow-up: the sample instructions named only Visual Studio 2026, while the requirements say Visual Studio 2022 17.14 also builds the projects.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The samples (and scripts/uno-template, which port-to-uno.ps1 copies) listed
net*-ios and net*-maccatalyst but had no Platforms/iOS or Platforms/MacCatalyst
folder, so those heads could not build (Uno.Sdk looked for iOS/Info.plist).
Each project now has Info.plist, Entitlements.plist and an entry point for both,
from Uno.Templates 6.7.45 (iOS) and 5.6.54 (Mac Catalyst, which the 6.x templates
no longer scaffold), both started with UnoPlatformHostBuilder.UseAppleUIKit().
The PR build matrix builds ios and maccatalyst again on macos-15.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@turbobobbytraykov

Copy link
Copy Markdown
Contributor Author

Done: on .NET 10 every platform builds except Mac Catalyst, which fails to link the iOS-only Uno.icu-ios library (the same failure as on .NET 9). Closing this temporary PR and deleting its branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant