[Blazor] Validate component metadata under Native AOT - #68302
Draft
javiercn wants to merge 1 commit into
Draft
Conversation
javiercn
force-pushed
the
javiercn-aspire-dashboard-aot-strict-proof
branch
from
August 9, 2026 19:46
14cc38b to
7f60778
Compare
Disable the STJ, component metadata, and JS-invokable reflection fallbacks in the strict feature app, promote incomplete generated metadata to errors, and require ILC warnings as errors. Keep unsupported HTTP form mapping outside the proof image through a strict-test-only substitution. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
javiercn
force-pushed
the
javiercn-aspire-dashboard-aot-strict-proof
branch
from
August 9, 2026 22:01
7f60778 to
7274404
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Layer 6 of 6 for Aspire Dashboard Native AOT support. Depends on #68300.
This PR is strict proof only: it adds no product scenario, product fix, provider, or root. There is no second matrix commit because strict execution requires only the project/target wiring in the single proof commit; no scenario source changed. The intentional
JitDefaultreflection-compatibility witness remains JIT-only.Validation
The full build used
C:\Nuget\microsoft.wix\6.0.3-dotnet.6\tools\net6.0\anyonPATH. The initial WiXWIX0001was environmental: App.Ref correctly stagesMicrosoft.Extensions.Configuration.Binder.SourceGeneration.dllfromMicrosoft.Internal.Runtime.AspNetCore.Transport, but this worktree gives the staged payload a 259-character absolute path and WiX native reports it as missing. Building App.Ref from a shortR:mapping succeeded and proved the owner graph/output. The final clean full build used that short mapping plus an isolated copy of the selected VS MSBuild with the SDK's exact net472 NuGet task dependencies;Common7,VC, and managed rule-set directories remained junctioned to the installed VS instance. No source or project file was changed for the workaround.Donor remainder audit
Audited cumulative final parent
58a0cfee0109e9f8313905d0b868fb3a84874fdbplus this PR against frozen sourcec7f68e2bdcc266063545aae1b45335e0d5bdc758/ treede914584c9e52969b921e3e3195a8ce4edac2678after the final PR2 CI-fix cascade restack.