Skip to content

Add the WinUI XAML language service as a Native AOT language server - #276

Merged
Chiara Mooney (chiaramooney) merged 226 commits into
mainfrom
chiaramooney-native-aot-compatibility
Nov 2, 2026
Merged

Chiara Mooney (chiaramooney) merged 226 commits into
mainfrom
chiaramooney-native-aot-compatibility

Conversation

@chiaramooney

@chiaramooney Chiara Mooney (chiaramooney) commented Oct 1, 2026 •

Copy link
Copy Markdown
Collaborator

Description

Resolves #52
Closes #115
Closes #209
Closes #213
Closes #214
Closes #215
Closes #220

Adds a WinUI 3 XAML language service to the extension: a packaged Native AOT language server (win-x64 and win-arm64) that gives .xaml files project-aware editing on top of the existing syntax highlighting.

What it provides — completion for elements, properties, events, attached properties, enum and bool values, markup extensions, and resource keys, resolved against your app source and its referenced projects; hover; Go to Definition into C# (event handlers, x:Bind members, x:Name, resource keys); syntactic and semantic diagnostics; find-all-references; rename; formatting; semantic tokens; and code actions that import types, add xmlns declarations, insert x:DataType, repair bindings and Setter properties, and generate event handlers.

It starts without .NET. The server is self-contained with the runtime linked in, so it launches on a machine with nothing installed. .NET SDK is a requirement of the project-aware features, not of the editor — which makes the requirement follow your project language:

  • C++/WinRT — no .csproj, so MSBuild and the generator host are never invoked. Formatting, folding, outline, close-tag completion, document links, and syntax diagnostics all work with no .NET at all.
  • C# — needs the .NET 10 SDK for type-aware completion, x:Bind checking, and navigation. Without it the server still runs and the status bar reports WinApp: .NET SDK Required for XAML IntelliSense with an install link.

The extension never installs a runtime or SDK; it links to the official download page.

Loading is staged, not blocking. Language-independent features are live immediately; WinUI SDK and package types resolve at the framework-ready stage; your own source types and semantic diagnostics complete the load. The status bar reports which stage the active document is in, and completion results served early are marked incomplete so VS Code re-queries automatically.

Projects that were never built still resolve. A design-time build via dotnet msbuild builds referenced projects. Unrestored packages are restored automatically in a trusted workspace; an untrusted one is never restored and offers Restore Packages instead. A reference with real compiler errors is reported as WinApp: Referenced Project Failed to Build with a Build action, not silently worked around.

When the server cannot start — untrusted workspace, a non-Windows or non-x64/ARM64 host, or a startup failure — XAML editing degrades to syntax highlighting rather than failing outright, with a one-time notification naming the cause.

image

Native AOT boundary

Native AOT changes what needs .NET, not just how the server starts, so two pieces deliberately stay outside the native process:

  • MSBuild evaluation and restore run through the dotnet CLI. MSBuildLocator resolves assemblies from the user's installed SDK at runtime and AOT has no assembly loader, so this cannot be linked in.
  • Source generators run in a framework-dependent host (WinUiXaml.GeneratorHost.dll), because running them means loading your project's analyzer assemblies at runtime.

LSP traffic uses a source-generated JsonSerializerContext rather than reflection-based System.Text.Json. Packaging validates that the VSIX carries a Native AOT binary for every shipping architecture and no CoreCLR runtime files; the binaries are ESRP-signed by the official release pipeline, not by CI builds, so artifacts from build.yml are unsigned by design. The dotnet host is always resolved to an absolute path — a bare name would otherwise resolve against the project directory before PATH, so a planted dotnet.exe could win. There is no bare-name fallback on either side: resolveDotnetCommand() returns an absolute path or undefined, and the server's MsBuildCli.DotnetPath prefers DOTNET_HOST_PATH, then scans PATH and the well-known install roots, and reports the missing-SDK error rather than guessing.

Type of Change

  • ✨ New feature
  • 🔧 Config/build

Checklist

  • New tests added for new functionality (if applicable)
  • Ran .\scripts\build-vsce.ps1 locally
  • Tested locally on Windows (if applicable)
  • README.md updated (if applicable)
  • CONTRIBUTING.md updated (if contributor workflow changed)
  • package.json contribution points / command/debugger/custom-editor docs updated (if extension surface changed)

Additional Notes

Validation

Command Result
npx tsc --noEmit clean
npm run test:unit 1134 passing / 0 failing
npm run test:server 1169 passing / 0 failing
npm run test:xaml-smoke PASS
XAML integration client (WINUI_XAML_TEST_FILES=test/xaml-integration/client.test.js) 10 passing
npm run lint 0 errors, 12 pre-existing warnings
.\scripts\build-vsce.ps1 SUCCESS

The smoke suite drives real LSP traffic over stdio against the packaged server, and the integration suite includes a test that forces the server to start with no .NET available and asserts semantic tokens still arrive — that is the load-bearing defense of the "starts without .NET" claim, and it was mutation-verified.

Review history

Several rounds of the repo's pr-review skill ran against this branch; each round's findings were adjudicated with a cross-model check and fixed in a dedicated commit. Security-relevant assertions were mutation-tested — each test was confirmed to fail against a regressed implementation before being trusted.

Review guidance

This is a large diff because it introduces the server, its test suites, and the packaging path together. Suggested reading order:

  1. README.md (XAML Language Service section) — user-facing behavior and the status-bar contract.
  2. src/xaml/ — the extension-side client: lifecycle, status, notifications, and dotnet resolution.
  3. server/src/ — the language server itself.
  4. scripts/ and .github/workflows/build.yml — how the native server is built, signed, bundled, and validated.

Nikola Metulev (nmetulev) and others added 30 commits August 6, 2026 14:49
Folds the hardened XAML language service prototype (nmetulev/winui-vsc) into the shipping winapp VS Code extension as a single unified extension. Additive and non-breaking to the existing winapp CLI / debug / manifest features.

Server: copy the .NET 10 LSP server (WinUiXaml.LanguageServer/Workspace/Xaml + 3 xUnit test projects + WinUiXaml.slnx + lsp-smoke) under server/. Builds 0/0; 489/489 unit tests pass.

Client: add src/xaml/xamlLanguageService.ts (activateXaml/deactivateXaml, resolveServerDll bundled->dev fallback) wired additively from src/extension.ts; degrades to syntax-only on server-start failure. Contribute the xaml language, TextMate grammar, language-configuration, winui-xaml.showInfo|restartServer commands, winui-xaml.server.* config, onLanguage:xaml activation, and the vscode-languageclient ^9 dependency in package.json.

Tests: port the 81-file integration harness to test/xaml-integration/ (kept as source of truth) with a clean committed WinAppSDK fixture at test/fixtures/xaml/fixture/ and a root .vscode-test.mjs. Full suite: 1596 passing / 28 pending / 0 failing. smoke.mjs and features.test.js (218) green.

Packaging/CI: esbuild + package-vsc.ps1 publish the server into dist/server (bundled in the VSIX); .vscodeignore excludes C# sources/tests; release-vsc.yml adds UseDotNet@2, a server publish step, and a conditional ESRP DLL-signing step for our own WinUiXaml.*.dll.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 03c713cc-41ae-4c28-ab49-3c851aa8e2bd
Automated fix->review loop iteration 1 — resolves all 17 findings from the
post-migration PR review (2 High, 9 Medium, 6 Low):

- H1 security: machine-scope winui-xaml.server.path/dotnetPath + workspace-trust
  gate (isTrusted + onDidGrantWorkspaceTrust) + capabilities.untrustedWorkspaces
- H2: deterministic fixture NuGet restore (restore:fixture in pretest)
- M1: run XAML/server/smoke suites in CI with .NET 10 (setup-dotnet)
- M2: document .NET-dependent suites; unit tests stay dotnet-free
- M3/M4: README Features + Requirements for the XAML language service
- M5: serialize client start/stop lifecycle (no torn-down pending start)
- M6: handle workspace/didChangeWatchedFiles (invalidate stale Roslyn cache)
- M7: user-facing "degraded to syntax-only" notification with actions
- M8: client command/lifecycle/degradation integration tests
- M9: fold server bundling into vscode:prepublish (ensure-server-bundle.mjs)
- L1: share bundled-asset path resolver (firstExistingPath)
- L2: tighten .vscodeignore + VSIX-contents assertion
- L3/L4: README command table + CONTRIBUTING .NET 10 SDK prereq
- L5/L6: docs/RELEASE.md signing checklist + server/nuget.config feed pin

Verified: tsc clean, eslint 0 errors, server build 0/0, 489/489 server tests,
smoke PASS, integration 1601 passing / 0 failing.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 03c713cc-41ae-4c28-ab49-3c851aa8e2bd
Automated fix->review loop iteration 2 — resolves the 5 residual/new findings
the independent GPT-5.6 review raised on iteration 1:

- N1 (CRITICAL security): do not start the semantic server while the workspace
  is untrusted (Roslyn/MSBuild would evaluate an attacker-controlled .csproj and
  could execute code). Stay syntax-only until trust is granted; test host runs
  with --disable-workspace-trust so the feature suite still exercises the server.
- N2 (correctness): replace the partial start-guard with a single lifecycle
  queue (runExclusive) so stop fully completes before any start — two servers
  can never coexist across concurrent restarts.
- N3 (correctness): null-guard workspace/didChangeWatchedFiles (changes:null).
- N4 (test-coverage): WINUI_XAML_FORCE_NO_SERVER test seam + a real absent-DLL
  degradation test (syntax-only, no throw).
- N5 (packaging): ensure-server-bundle publishes fresh by default; reuse only
  under WINUI_REUSE_SIGNED_SERVER=1 (set by CI -SkipServerBuild) to preserve
  signed DLLs, so a bare vsce package can never ship a stale server.

Verified: tsc clean, eslint 0 errors, server build 0/0, 489/489 server tests,
smoke PASS, integration 1602 passing / 0 failing.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 03c713cc-41ae-4c28-ab49-3c851aa8e2bd
…(P1-P3)

P1 (M5 residual): guard against server resurrection when restart races
deactivate. Add module-level `disposing` flag set synchronously at the top
of deactivateXaml and reset in activateXaml; doStart early-returns when
disposing. Replace the separate stop+start in the restartServer command and
onDidGrantWorkspaceTrust with a single restartClient() that runs
stop-then-start inside one runExclusive op (atomic; skips start if disposing).

P2: rewrite package.json untrustedWorkspaces capability description to match
actual behavior (syntax highlighting only until the workspace is trusted).

P3 (M9 residual): package-vsc.ps1 -SkipServerBuild set WINUI_REUSE_SIGNED_SERVER
into the caller's environment and never cleaned it up. Capture the prior value
before the try and restore/remove it in the finally block.

Full integration suite: 1602 passing / 0 failing.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 03c713cc-41ae-4c28-ab49-3c851aa8e2bd
…packaging)

Final 8-dimension PR-review gate over the whole branch surfaced 10 findings the
per-iteration reviews (scoped to their own residuals) never looked at. Fix all.

G1 (HIGH security): the isTrusted gate is necessary but not sufficient — an empty
window is trusted, so opening a loose XAML file outside any workspace folder made
the server warm up and MSBuild-evaluate its nearest .csproj (code-exec vector).
Client now passes workspaceFolders as initializationOptions.allowedRoots; the
server (ResolveAllowedRoots/IsPathUnderAllowedRoot/ResolveIfAllowedAsync) only
runs project discovery + OpenProjectAsync for documents under a trusted root.
Empty allow-list => no project evaluation; out-of-root/untitled files are served
project-less (tolerant parser only). Boundary-aware, case-insensitive path check.
allowedRoots is authoritative when present; legacy clients fall back to rootUri.

G3 (HIGH test-coverage): add WINUI_XAML_FORCE_UNTRUSTED seam (mirrors
WINUI_XAML_FORCE_NO_SERVER) so the trust gate + onDidGrantWorkspaceTrust recovery
are exercised under the trusted harness. New client tests cover degrade+recover.

G4 (docs): document winui-xaml.server.path in README.
G5 (correctness): retain the synchronize.fileEvents FileSystemWatcher and dispose
it in doStop / failed-start catch (was leaking one per start/restart/trust cycle).
G6 (UX): untrusted degradation now shows a once-per-transition warning with a
Manage Workspace Trust action (was log-only).
G7 (test-coverage): extract pure buildDegradedNotification() + unit test message
and action mapping.
G8 (test-coverage): client tests for explicit server.path (valid -> semantic
completion; invalid -> syntax-only, no throw).
G9 (test-coverage): lsp-smoke sends didChangeWatchedFiles with omitted/null/empty
changes and asserts the server stays responsive.
G10 (packaging): drop the redundant bundle:server in package-vsc.ps1 (vscode:
prepublish/ensure-server-bundle.mjs is the single publish path).
G2 (packaging): narrow .vscodeignore to exclude only the apphost exe so Roslyn's
net472 MSBuild BuildHost.exe ships; assert a BuildHost is present in the VSIX.

Full integration 1605 passing / 0 failing; server 489, unit 595, smoke green.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 03c713cc-41ae-4c28-ab49-3c851aa8e2bd
…indings)

The final 8-dimension confirmation gate (incl. a cross-model check) found 5 issues
the per-iteration reviews never scoped. Fix all 5.

G15 (HIGH security): the allow-list was purely lexical — Path.GetFullPath does not
resolve reparse points, so a junction/symlink placed inside a trusted workspace root
that targets an external directory passed the containment check, and the resolver
(FindOwningProject -> MSBuild GetOrLoadAsync) then evaluated the external .csproj.
Fix: CanonicalizePath resolves the final physical path (GetFinalPathNameByHandle) for
both the workspace roots (NormalizeRoots) and the document (IsPathUnderAllowedRoot)
before containment; falls back to the lexical full path for non-existent/untitled
docs or on any OS-call failure. A junction escaping the root now canonicalizes
outside it and is served project-less.

G11 (MEDIUM correctness): a workspace opened at a bare drive root (C:\) rejected all
its children — NormalizeRoots keeps C:\ with its trailing separator, but PathIsWithin
required path[root.Length] to be a separator (it was the first path-segment letter).
Fix: when the root already ends in a separator (bare drive/UNC root) the prefix match
is itself the boundary. The boundary-char check still guards C:\root vs C:\rootEvil.

G12 (HIGH test-coverage): the security-critical boundary had no direct test. Made
NormalizeRoots/PathIsWithin/CanonicalizePath internal (test project already has
InternalsVisibleTo) and added AllowedRootBoundaryTests (exact/child/out-of-root/
sibling-prefix/drive-root/cross-drive/case/trailing-sep/normalize-trim + a non-admin
mklink /J junction regression). Added a behavioral lsp-smoke case: a document under
os.tmpdir (outside the sole allowedRoot) gets no project-backed resolution while the
in-root fixture still resolves.

G13 (MEDIUM UX): the degraded-notification guard was a single boolean reset only on a
successful start, so after a user granted trust but the server still could not start
(e.g. no dotnet) the server-missing guidance was suppressed. Fix: track the last
degraded cause and notify once per distinct cause (untrusted vs server), still
non-nagging; reset on successful start.

G14 (LOW docs): README used the abbreviated server.dotnetPath; use the full
winui-xaml.server.dotnetPath.

Full integration 1605 passing / 0 failing; server 505, unit 595, smoke green;
server debug build 0 warnings.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 03c713cc-41ae-4c28-ab49-3c851aa8e2bd
…trust boundary

reviewer-iter5 (independent cross-model) found two HIGH residuals in the iter5
allow-list hardening. Both are closed here.

G15 (security) — the canonicalizer only resolved reparse points for an EXISTING
leaf (CreateFileW/OPEN_EXISTING). A not-yet-created XAML leaf under an in-root
junction (e.g. C:\trusted\link\Page.xaml, no file) failed that call and fell back
to the lexical path, which still passed lexical containment. XamlProjectResolver
.FindOwningProject only needs the DIRECTORY (new FileInfo(path).Directory +
dir.GetFiles("*.csproj")), so the external junction target's .csproj was still
MSBuild-evaluated — a code-exec bypass. CanonicalizePath now walks up to the
deepest EXISTING ancestor (which follows any junction/symlink in the ancestry),
resolves it via GetFinalPathNameByHandle, and re-appends the missing tail; lexical
fallback is used only when no ancestor exists or the OS call fails. Legit
not-yet-saved files under a real (non-junction) dir still resolve in-root, so
IntelliSense for new files is preserved.

G12 (test-coverage) — the junction regression test never created the linked file,
so it exercised the same missing-leaf fallback, and its Assert.False threw inside a
broad catch(Exception) that swallowed the failure: a green test over a live hole.
The test now creates the linked file and asserts BOTH the existing-leaf and the
missing-leaf paths canonicalize OUTSIDE the trusted root, with the assertions moved
out of the swallowing catch (it skips only on genuine junction-creation failure).
The out-of-root lsp-smoke case gains a sibling .csproj + code-behind so the null F12
result is attributable to the trust gate rather than to an absent project.

Verification: build:server:debug 0 warnings/0 errors; test:server 505/505 (junction
test genuinely exercised — junctions confirmed creatable in this env);
test:xaml-smoke PASS incl. the strengthened out-of-root case; full integration
1605 passing / 0 failing / 28 pending.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 03c713cc-41ae-4c28-ab49-3c851aa8e2bd
- test:xaml-smoke now runs restore:fixture before the smoke harness so
  element completion has WinUI SDK metadata in CI. The fixture's obj/ is
  gitignored and was previously only restored by the integration pretest,
  so the standalone smoke step failed in CI with 0 completion items. This
  unblocks build-and-test and the packaged VSIX artifact.
- redteam-gap4.test.js: use replaceAll for the caret-marker strip
  (CodeQL "incomplete string escaping or encoding").
- redteam19.test.js: drop the no-op self-replacement
  (CodeQL "replacement of a substring with itself").
- pr-description.yml: tolerate the REST diff API's 20k-line cap (HTTP 406)
  on very large PRs instead of failing; fall back to the changed-file list.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 03c713cc-41ae-4c28-ab49-3c851aa8e2bd
CodeQL's full scan of the migrated test files (features.test.js, smoke.mjs)
flagged sanitization patterns in test helpers. All fixes are behavior
preserving (smoke PASS; integration 1605 passing / 0 failing):

- caret-marker strip: .replace("|", "") -> .replaceAll("|", "")
  (js/incomplete-sanitization).
- exact completion-label membership: array.includes(<uri>) ->
  array.some((l) => l === <uri>) — these were array-membership checks that
  CodeQL misread as URL substring checks (js/incomplete-url-substring-sanitization).
- diagnostic display string: drop the nested template literal in favor of
  string concatenation (js/bad-code-sanitization).

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 03c713cc-41ae-4c28-ab49-3c851aa8e2bd
Build local native bundles, consume signed release artifacts, harden workspace boundaries and lifecycle behavior, and validate both packaged architectures.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Keep bundled mode fail-closed for fallback resolution while allowing authoritative custom path settings to exercise degradation and recovery. Avoid secondary artifact-upload failures when an earlier CI gate fails.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Keep the canonical x:Bind diagnostics in redteam15 and clarify that the prefix-sharing resource tests exercise references and document highlights separately.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Add merged resource traversal, semantic binding diagnostics, namespace cleanup, on-type formatting, snippets, and surround-with refactors with full server and live VS Code coverage.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Distinguish language-server completions from VS Code word suggestions and align resource and attached-property assertions with current behavior.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Shorten comments, split oversized server and test files, remove unrelated release and CLI downloader changes, and rename red-team tests by scenario.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Remove static color, font-weight, and theme-resource tables; source completion data from project metadata and generic.xaml. Also remove standalone snippets, Surround With, and user-facing server path overrides.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Use a member-only completion edit range so VS Code can display property-element items after the owner dot, and lock the edit shape down with regression coverage.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10
Ask VS Code to open value completion after accepting an attribute snippet when the resolved property or event has value candidates. Cover scalar, event, and attached-property cases plus the serialized LSP command.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d48e3dcd-70ba-416d-b66e-e5f046facd10

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 AI-generated review (WinAppVSCE pr-review skill) — verify before acting.

Reviewed 9dcfcca against the previous review. All six feedback groups are addressed: project-reference configuration fidelity, rename safety, generated-handler signatures, child-process cleanup, path authorization, and the Native AOT support contract. The original reproductions now behave correctly, and I found no new blocking defects in the delta.

Approving the reviewed changes. The main build-and-test CI check is still running at submission time; this approval does not replace that remaining merge gate. Signed release ARM64 execution remains tracked separately.

Require the generated Click handler's fully qualified RoutedEventArgs type
so the VS Code test matches the import-independent code generation contract.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 0a32116a-78ec-415a-aa5e-f98a06c74e9d
@chiaramooney
Chiara Mooney (chiaramooney) merged commit 897dcf6 into main Nov 2, 2026
7 checks passed
@chiaramooney
Chiara Mooney (chiaramooney) deleted the chiaramooney-native-aot-compatibility branch November 2, 2026 19:51
This was referenced Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agent-preparing Agent work in progress (feedback, validation, or CI)

Projects

None yet

5 participants