fix: isolate .NET 11 Razor support in preview builds - #11176
Merged
Merged
Conversation
vicancy
marked this pull request as ready for review
September 24, 2026 01:39
vicancy
force-pushed
the
codex/fix-net11-razor
branch
from
September 24, 2026 01:41
79e7954 to
736e451
Compare
vicancy
marked this pull request as draft
September 24, 2026 02:31
vicancy
force-pushed
the
codex/fix-net11-razor
branch
from
September 24, 2026 02:38
736e451 to
4448c36
Compare
vicancy
marked this pull request as ready for review
September 24, 2026 02:43
vicancy
force-pushed
the
codex/fix-net11-razor
branch
2 times, most recently
from
September 24, 2026 05:34
1dd3822 to
d0c5801
Compare
vicancy
force-pushed
the
codex/fix-net11-razor
branch
from
September 24, 2026 05:38
d0c5801 to
f8eb636
Compare
This was referenced Sep 25, 2026
This was referenced Sep 25, 2026
Merged
This was referenced Sep 28, 2026
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.
Related to #11171.
Add opt-in net11.0 DocFX assets for the .NET 11 RC1 Razor source generator while preserving stable compiler dependencies in ordinary builds. Measure every nightly tool target so the compatibility report exposes both the fix and the older tools' remaining limitations.
RoslynVersionproperty selects the version per target for all eight compiler packages.DOCFX_PREVIEW_BUILD=trueadditionally builds net11.0 with Roslyn5.11.0-1.26425.128; the public preview restore source and experimental symbol API adaptations apply only to net11.0.Tool target and project target are independent. SDK 11 Razor projects need the net11.0 preview tool even when the project targets net10.0. Older tools retain stable Roslyn and their incompatibilities remain visible. Direct consumers of the preview
Docfx.Dotnetnet11.0 library assets also need Microsoft's publicdotnet-toolssource.Full test and 50-case matrix evidence at
1dd3822:The net8.0/net9.0 tools are incompatible with SDK 10 and SDK 11 Razor; the net10.0 tools are incompatible with SDK 11 Razor. SDK 11 is tested with both net10.0 and net11.0 projects. These observations remain visible and do not block reporting mode.
All 55 reporting tests pass, including 50 distinct case identities, missing-target and fallback detection, package identity, rendering, and archive export. A local 24-case comparison also completes without environment errors. Inspection of the actual package confirms stable Roslyn for net8.0/net9.0/net10.0 and preview Roslyn only for net11.0.
Current-head verification (
f8eb636c2): complete normal and preview solution restores pass. The resolved dependency graphs for all four targets match the previous configuration exactly, including the net8.0/net9.0 exact version pins; ordinary restore uses no preview feed.