Add .NET 10 obsolescence note to Razor runtime compilation docs#36722
Merged
Add .NET 10 obsolescence note to Razor runtime compilation docs#36722
Conversation
Co-authored-by: tdykstra <1569635+tdykstra@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add note to Razor runtime compilation documentation about obsolescence
Add .NET 10 obsolescence note to Razor runtime compilation docs
Jan 30, 2026
tdykstra
reviewed
Jan 30, 2026
Clarified note on runtime compilation obsolescence in .NET 10.
wadepickett
reviewed
Feb 2, 2026
wadepickett
reviewed
Feb 2, 2026
wadepickett
approved these changes
Feb 2, 2026
Contributor
wadepickett
left a comment
There was a problem hiding this comment.
Approved, but I also left some notes to consider, but not required.
tdykstra
approved these changes
Feb 2, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds obsolescence notes to the Razor runtime compilation documentation to inform users that the feature was obsoleted in .NET 10. The changes direct users to use Hot Reload as the recommended alternative for development scenarios.
Changes:
- Added metadata fields
ai-usage: ai-assistedand updatedms.dateto01/30/2026 - Replaced the first NOTE block (lines 18-25) with a bold obsolescence statement linking to the compatibility documentation
- Updated the second NOTE block (line 28) to include an obsolescence statement before the existing Hot Reload recommendation
This was referenced Feb 3, 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.
Razor runtime compilation was obsoleted in .NET 10, but the documentation didn't reflect this status or recommend the preferred alternative (Hot Reload).
Fixes #36658
Changes
ms.dateto01/30/2026and addedai-usage: ai-assistedBoth locations link to the official compatibility documentation:
/dotnet/core/compatibility/aspnet-core/10/razor-runtime-compilation-obsoleteThe obsolescence note appears prominently at the top of the article where runtime compilation is first introduced, and again where Hot Reload is discussed as the alternative.
Original prompt
This section details on the original issue you should resolve
<issue_title>Add note to the Razor runtime compilation doc that it is obsolete</issue_title>
<issue_description>### Description
We obsoleted Razor runtime compilation in .NET 10: https://learn.microsoft.com/dotnet/core/compatibility/aspnet-core/10/razor-runtime-compilation-obsolete. We should add a note to the Razor runtime compilation doc clarifying that it is obsolete and recommend using Hot Reload instead for development scenarios.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/mvc/views/view-compilation?view=aspnetcore-10.0&tabs=visual-studio
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/mvc/views/view-compilation.md
Document ID
16438f35-f35d-c097-0903-ec17e83e051e
Platform Id
de165183-f986-f872-0447-6c3550b1c278
Article author
@tdykstra
Metadata
Related Issues</issue_description>
Comments on the Issue (you are @copilot in this section)
@wadepickett @tdykstra @tdykstra ## 🤖 AI Triage SummaryThis preliminary assessment report was run by: @tdykstra
Date: 2026-01-29
Issue: 36658
Model: GitHub Copilot
Issue Analysis: Add note to the Razor runtime compilation doc that it is obsolete
✅ Issue Validation
Status: Valid and actionable
📋 Issue Summary
Razor runtime compilation was obsoleted in .NET 10, but the “Razor file compilation in ASP.NET Core” article currently discusses enabling runtime compilation without clearly stating its obsolescence status for .NET 10+ readers. The issue requests adding a note in the article to clarify that runtime compilation is obsolete (in .NET 10) and to recommend using Hot Reload for development scenarios.
This is a documentation-only change, in scope for ASP.NET Core docs, and can be addressed by updating the existing article.
🔎 Information gathered
aspnetcore/mvc/views/view-compilation.md📁 Potentially Affected Files
aspnetcore/mvc/views/view-compilation.mdaspnetcore/mvc/views/view-compilation.md📝 Preliminary Change Assessment
Potential documentation updates (primary)
File:
aspnetcore/mvc/views/view-compilation.mdThere are two obvious places to add an “obsolete in .NET 10” callout:
Option A (recommended): Update the first NOTE block near the top (most visible)
Location: Lines 17-24 (the NOTE block titled “Runtime compilation:”)
Type: Add a bullet and/or add a sentence with link to the compatibility note.
Current content (lines 17-24):
Suggested direction (example text):