Add .NET 10 obsolescence note to Razor runtime compilation docs

[Copilot]

Razor runtime compilation was obsoleted in .NET 10, but the documentation didn't reflect this status or recommend the preferred alternative (Hot Reload).

Changes

• First NOTE block (lines 18-25): Added bullet point stating obsolescence in .NET 10 with link to compatibility note
• Second NOTE block (lines 33-34): Strengthened existing Hot Reload recommendation with explicit obsolescence statement
• Metadata: Updated ms.date to 01/30/2026 and added ai-usage: ai-assisted

Both locations link to the official compatibility documentation: /dotnet/core/compatibility/aspnet-core/10/razor-runtime-compilation-obsolete

The 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

• ID: 8a83deb2-e035-bb66-be4f-68709bcad341
• PlatformId: de165183-f986-f872-0447-6c3550b1c278
• Service: aspnet-core
• Sub-service: mvc

Related Issues</issue_description>

Comments on the Issue (you are @copilot in this section)

@wadepickett @tdykstra @tdykstra ## 🤖 AI Triage Summary

📌 Note to community: This is an automated preliminary analysis to help our documentation team quickly review, determine scope, and prioritize this issue. This report is not a resolution or final decision. A maintainer will review and may adjust the proposed approach.

---

This 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

• Issue: Add note to the Razor runtime compilation doc that it is obsolete #36658
• Published doc (target): https://learn.microsoft.com/en-us/aspnet/core/mvc/views/view-compilation?view=aspnetcore-10.0&tabs=visual-studio
• Source file: aspnetcore/mvc/views/view-compilation.md
• External reference: .NET compatibility note: https://learn.microsoft.com/dotnet/core/compatibility/aspnet-core/10/razor-runtime-compilation-obsolete

📁 Potentially Affected Files

These files have been identified as possibly related to this issue and may need review.

File	Path	Lines	Section
Main article	aspnetcore/mvc/views/view-compilation.md	13-35	Intro + first NOTE block (runtime compilation bullets)
Main article	aspnetcore/mvc/views/view-compilation.md	29-34	Hot Reload mention + NOTE recommending Hot Reload

📝 Preliminary Change Assessment

The following are initial observations for the documentation team to evaluate—not final decisions.

Potential documentation updates (primary)

File: aspnetcore/mvc/views/view-compilation.md

There 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):

> [!NOTE]
> Runtime compilation:
> * Isn't supported for Razor components of Blazor apps.
> * Doesn't support [global using directives](/dotnet/csharp/whats-new/csharp-10#global-using-directives).
> * Doesn't support [implicit using directives](/dotnet/core/tutorials/top-level-templates#implicit-using-directives).
> * Disables [.NET Hot Reload](xref:test/hot-reload).
> * Is recommended for development, not for production.

Suggested direction (example text):

> [!NOTE]
> Runtime compilation:
> ...
> * Is obsolete in .NET 10. F...

</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

- Fixes dotnet/AspNetCore.Docs#36658

<!-- START COPILOT CODING AGENT TIPS -->
---

✨ Let Copilot coding agent [set things up for you](https://github.com/dotnet/AspNetCore.Docs/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo.


<!-- PREVIEW-TABLE-START -->

---

#### Internal previews

| 📄 File | 🔗 Preview link |
|:--|:--|
| [aspnetcore/mvc/views/view-compilation.md](https://github.com/dotnet/AspNetCore.Docs/blob/4ac769e9326335d63460314f4e9e38827f82b7b7/aspnetcore/mvc/views/view-compilation.md) | [Razor file compilation in ASP.NET Core](https://review.learn.microsoft.com/en-us/aspnet/core/mvc/views/view-compilation?branch=pr-en-us-36722) |


<!-- PREVIEW-TABLE-END -->