Remove unused usings

[smiller7812]

Description

These are the only three namespaces I need for the Index page:

using Microsoft.AspNetCore.Mvc.RazorPages;
using Microsoft.EntityFrameworkCore;
using RazorPagesMovie.Models;

You might want to right click on the using statements at the top of all your pages and select "Remove and Sort Usings" to get rid of unneeded usings.
As you write code if you let intelligence finish off class names [hit tab] the VS IDE automatically inserts the needed using statement back in.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/tutorials/razor-pages/page?view=aspnetcore-10.0&tabs=visual-studio

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/tutorials/razor-pages/page.md

Document ID

15e79e80-8d46-7cd5-c883-6cc0f5940a1b

Platform Id

c731bb82-fefd-1cfc-91d3-8ea9527d2680

Article author

@wadepickett

Metadata

• ID: 70f6104a-a223-4bb3-4101-f553002b9b26
• PlatformId: c731bb82-fefd-1cfc-91d3-8ea9527d2680
• Service: aspnet-core
• Sub-service: tutorials

Related Issues

---

Associated WorkItem - 558794

[wadepickett]

Thanks @smiller7812 for taking the time to file this issue. You are right, that should be reviewed.

The tutorial does need to reflect what the developer would see on their own screen when project or scaffolding templates are used. The templates in some cases put in using statements that would be useful, but are not used in the focused tutorial example. I would guess however there are some in there that are not added by the templates, and yet not used. I'll check.

[wadepickett]

🤖 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 answer to your question—it's an internal triage tool that identifies potentially relevant docs, code samples, and versions to look into. A team member will review this issue and respond. Thank you for your contribution!

---

This preliminary assessment report was run by: @wadepickett
Date: 2026-03-05
Issue: 36838
Model: GitHub Copilot

---

Issue Analysis: Remove unused usings from Razor Pages tutorial code samples

✅ Issue Validation

Status: Valid — but requires nuanced action based on scaffolding template analysis

📋 Issue Summary

The issue requests removing unnecessary using statements from code samples in the Razor Pages tutorial. However, investigation of the actual ASP.NET Core scaffolding templates in dotnet/Scaffolding reveals that the using statements present in the documentation samples are intentionally generated by the scaffolding tooling that the tutorial instructs users to run. The tutorial should match what users actually see when following along.

Key Finding: Two Generations of Scaffolding Templates

The dotnet/Scaffolding repository contains two scaffolding codepaths:

Scaffolder	Used By	Usings Generated	Tutorial Uses It?
Old scaffolder (VS.Web.CG.Mvc / aspnet-codegenerator)	VS "Add Scaffolded Item" UI + dotnet aspnet-codegenerator CLI	Verbose: includes System;, System.Collections.Generic;, System.Linq;, System.Threading.Tasks;, Microsoft.AspNetCore.Mvc.Rendering;, etc.	Yes — both the VS tab and VS Code tab use this scaffolder
New scaffolder (dotnet-scaffold / T4 templates under net10.0/)	dotnet scaffold aspnet razorpages-crud CLI	Minimal: only Microsoft.AspNetCore.Mvc;, Microsoft.AspNetCore.Mvc.RazorPages;, Microsoft.EntityFrameworkCore; + dynamic model/context namespaces	No — the tutorial does not currently instruct users to use this

Evidence from the old scaffolder templates (CreatePageModel.cshtml):

using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;
using Microsoft.AspNetCore.Mvc;
using Microsoft.AspNetCore.Mvc.RazorPages;
using Microsoft.AspNetCore.Mvc.Rendering;

Evidence from the new .NET 10 scaffolder templates (IndexModel.tt):

using Microsoft.AspNetCore.Mvc;
using Microsoft.AspNetCore.Mvc.RazorPages;
using Microsoft.EntityFrameworkCore;

(Plus only dynamically-needed modelNamespace and dbContextNamespace.)

Tutorial Scaffolding Instructions (from model.md)

• Visual Studio tab (line 83): Instructs "Add > New Scaffolded Item" → uses old scaffolder
• VS Code tab (line 107): Instructs dotnet aspnet-codegenerator razorpage → uses old scaffolder

Both tutorial paths use the old scaffolder, which generates the verbose usings. The snapshot-sample10 files correctly reflect what users will see.

📁 Detailed File Analysis

The table below compares each doc sample file's usings against what the scaffolding templates actually generate, and identifies which files match/mismatch.

snapshot-sample10 files (shown in the article via [!code-csharp] includes)

File	Path	Lines	Current Usings	Old Scaffolder Generates	Match?	Action Needed
Index.cshtml.cs	snapshot-sample10/Pages/Movies/Index.cshtml.cs	5-14	System, System.Collections.Generic, System.Linq, System.Threading.Tasks, Microsoft.AspNetCore.Mvc, Microsoft.AspNetCore.Mvc.RazorPages, Microsoft.EntityFrameworkCore, RazorPagesMovie.Data, RazorPagesMovie.Models, Microsoft.AspNetCore.Mvc.Rendering	System, System.Collections.Generic, System.Linq, System.Threading.Tasks, Microsoft.AspNetCore.Mvc, Microsoft.AspNetCore.Mvc.RazorPages, Microsoft.EntityFrameworkCore, RazorPagesMovie.Data, RazorPagesMovie.Models	⚠️ Mostly — Mvc.Rendering is extra (not in Index template)	Consider removing Mvc.Rendering only
Create.cshtml.cs	snapshot-sample10/Pages/Movies/Create.cshtml.cs	2-10	System, System.Collections.Generic, System.Linq, System.Threading.Tasks, Microsoft.AspNetCore.Mvc, Microsoft.AspNetCore.Mvc.RazorPages, Microsoft.AspNetCore.Mvc.Rendering, RazorPagesMovie.Data, RazorPagesMovie.Models	System, System.Collections.Generic, System.Linq, System.Threading.Tasks, Microsoft.AspNetCore.Mvc, Microsoft.AspNetCore.Mvc.RazorPages, Microsoft.AspNetCore.Mvc.Rendering + dynamic namespaces	✅ Yes	No change needed
Delete.cshtml.cs	snapshot-sample10/Pages/Movies/Delete.cshtml.cs	1-9	System, System.Collections.Generic, System.Linq, System.Threading.Tasks, Microsoft.AspNetCore.Mvc, Microsoft.AspNetCore.Mvc.RazorPages, Microsoft.EntityFrameworkCore, RazorPagesMovie.Data, RazorPagesMovie.Models	System, System.Collections.Generic, System.Linq, System.Threading.Tasks, Microsoft.AspNetCore.Mvc, Microsoft.AspNetCore.Mvc.RazorPages, Microsoft.EntityFrameworkCore + dynamic namespaces	✅ Yes	No change needed
Details.cshtml.cs	snapshot-sample10/Pages/Movies/Details.cshtml.cs	1-9	System, System.Collections.Generic, System.Linq, System.Threading.Tasks, Microsoft.AspNetCore.Mvc, Microsoft.AspNetCore.Mvc.RazorPages, Microsoft.EntityFrameworkCore, RazorPagesMovie.Data, RazorPagesMovie.Models	System, System.Collections.Generic, System.Linq, System.Threading.Tasks, Microsoft.AspNetCore.Mvc, Microsoft.AspNetCore.Mvc.RazorPages, Microsoft.EntityFrameworkCore + dynamic namespaces	✅ Yes	No change needed
Edit.cshtml.cs	snapshot-sample10/Pages/Movies/Edit.cshtml.cs	1-10	System, System.Collections.Generic, System.Linq, System.Threading.Tasks, Microsoft.AspNetCore.Mvc, Microsoft.AspNetCore.Mvc.RazorPages, Microsoft.AspNetCore.Mvc.Rendering, Microsoft.EntityFrameworkCore, RazorPagesMovie.Data, RazorPagesMovie.Models	System, System.Collections.Generic, System.Linq, System.Threading.Tasks, Microsoft.AspNetCore.Mvc, Microsoft.AspNetCore.Mvc.RazorPages, Microsoft.AspNetCore.Mvc.Rendering, Microsoft.EntityFrameworkCore + dynamic namespaces	✅ Yes	No change needed

sample/RazorPagesMovie10 files (completed project linked at end of tutorial)

File	Path	Lines	Current Usings	Old Scaffolder Generates	Match?	Action Needed
Index.cshtml.cs	sample/RazorPagesMovie10/Pages/Movies/Index.cshtml.cs	1-5	Microsoft.AspNetCore.Mvc, Microsoft.AspNetCore.Mvc.RazorPages, Microsoft.AspNetCore.Mvc.Rendering, Microsoft.EntityFrameworkCore, RazorPagesMovie.Models	N/A (completed sample reflects later tutorial steps with search/filter)	✅ Appropriate	No change — this is the finished version after cleanup
Create.cshtml.cs	sample/RazorPagesMovie10/Pages/Movies/Create.cshtml.cs	1-9	Verbose (matches old scaffolder output)	Same as old scaffolder	✅ Yes	No change needed
Delete.cshtml.cs	sample/RazorPagesMovie10/Pages/Movies/Delete.cshtml.cs	1-9	Verbose (matches old scaffolder output)	Same as old scaffolder	✅ Yes	No change needed
Details.cshtml.cs	sample/RazorPagesMovie10/Pages/Movies/Details.cshtml.cs	1-9	Verbose (matches old scaffolder output)	Same as old scaffolder	✅ Yes	No change needed
Edit.cshtml.cs	sample/RazorPagesMovie10/Pages/Movies/Edit.cshtml.cs	1-10	Verbose (matches old scaffolder output)	Same as old scaffolder	✅ Yes	No change needed

📝 Preliminary Change Assessment

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

Finding: Most samples correctly reflect scaffolded output

The vast majority of the using statements in the doc samples match exactly what the old scaffolding templates generate. Since both the Visual Studio tab and VS Code tab in the tutorial instruct users to use the old scaffolder (aspnet-codegenerator / "Add Scaffolded Item"), users following the tutorial will see these verbose usings in their generated files. The doc samples should match.

One minor discrepancy: Index.cshtml.cs snapshot

File: snapshot-sample10/Pages/Movies/Index.cshtml.cs
Lines: 5-14 (within the #if FIRST_INDEX block / snippetFullFirstGenerated)
Type: Possible minor correction

Current code (lines 5-14):

using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;
using Microsoft.AspNetCore.Mvc;
using Microsoft.AspNetCore.Mvc.RazorPages;
using Microsoft.EntityFrameworkCore;
using RazorPagesMovie.Data;
using RazorPagesMovie.Models;
using Microsoft.AspNetCore.Mvc.Rendering;

What the old scaffolder's IndexPageModel template generates:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;
using Microsoft.AspNetCore.Mvc;
using Microsoft.AspNetCore.Mvc.RazorPages;
using Microsoft.EntityFrameworkCore;

Plus dynamic RazorPagesMovie.Data and RazorPagesMovie.Models. The old scaffolder's Index template does not include Microsoft.AspNetCore.Mvc.Rendering (that is only in the Create/Edit templates). So Mvc.Rendering on line 14 may be a minor discrepancy worth verifying by actually running the scaffolder.

Suggested direction: Verify by running the actual scaffolder. If confirmed, remove line 14 (using Microsoft.AspNetCore.Mvc.Rendering;) from the snippetFullFirstGenerated block only.

Broader consideration: Future tutorial update to new scaffolder

If/when the tutorial is updated to use the new dotnet scaffold aspnet razorpages-crud CLI (which uses the .NET 10 T4 templates), all code samples would need to be updated to reflect the minimal usings that the new scaffolder generates:

New scaffolder output (all page models)
using Microsoft.AspNetCore.Mvc;
using Microsoft.AspNetCore.Mvc.RazorPages;
using Microsoft.EntityFrameworkCore;
using RazorPagesMovie.Models; (dynamic)
using RazorPagesMovie.Data; (dynamic)

That would be a separate, larger effort tied to migrating the tutorial to the new tooling.

🎯 Suggested Action Plan

For documentation team review

1. Verify the Mvc.Rendering discrepancy in Index.cshtml.cs:

   • Run the actual old scaffolder (dotnet aspnet-codegenerator razorpage or VS "Add Scaffolded Item") targeting .NET 10 to confirm whether Microsoft.AspNetCore.Mvc.Rendering appears in the generated Index.cshtml.cs.
   • If it does not appear, remove it from snapshot-sample10/Pages/Movies/Index.cshtml.cs line 14.

2. No other sample file changes needed at this time:

   • All other usings in the snapshot and completed sample files match what the old scaffolder produces.
   • Removing them would cause a mismatch between the tutorial and what users see when following along.

3. Consider a future work item to migrate the tutorial to the new dotnet scaffold CLI:

   • The new .NET 10 scaffolder templates generate clean, minimal usings.
   • When the tutorial is updated to use the new tooling, all code samples should be regenerated to match.
   • This could be tracked as a separate issue.

4. Optionally close issue Remove unused usings #36838 with an explanation:

   • The verbose usings are intentionally generated by the scaffolding tooling the tutorial instructs users to use.
   • A link to the scaffolding templates as evidence would be helpful.

⚠️ Review Considerations

• The tutorial currently targets the old scaffolder — both the VS tab (model.md line 83) and the VS Code tab (model.md line 107).
• The new scaffolder (dotnet scaffold) uses T4 templates under net10.0/RazorPages/ that produce minimal usings — but the tutorial does not yet use it.
• Changing the usings without changing the scaffolding tooling instructions would cause a mismatch between what users generate and what the tutorial shows.
• Check if similar analysis is needed for older moniker includes (page9.md, page8.md, etc.).

🔗 References

• Published article: https://learn.microsoft.com/en-us/aspnet/core/tutorials/razor-pages/page?view=aspnetcore-10.0&tabs=visual-studio
• Content source (page.md): aspnetcore/tutorials/razor-pages/page.md
• Content source (model.md — scaffolding instructions): aspnetcore/tutorials/razor-pages/model.md
• Old scaffolder Create template: VS.Web.CG.Mvc/Templates/RazorPageGenerator/Bootstrap5/CreatePageModel.cshtml
• New scaffolder .NET 10 Index template: net10.0/RazorPages/IndexModel.tt
• New scaffolder .NET 10 Create template: net10.0/RazorPages/CreateModel.tt
• Related issues: Search by Document ID

[smiller7812]

Sure thing. Glad it could help:)

…

________________________________ From: Wade Pickett ***@***.***> Sent: Thursday, March 5, 2026 2:14 PM To: dotnet/AspNetCore.Docs ***@***.***> Cc: Samuel Miller ***@***.***>; Mention ***@***.***> Subject: Re: [dotnet/AspNetCore.Docs] Remove unused usings (Issue #36838) [https://avatars.githubusercontent.com/u/10985336?s=20&v=4]wadepickett left a comment (dotnet/AspNetCore.Docs#36838)<#36838 (comment)> Thanks @smiller7812<https://github.com/smiller7812> for taking the time to file this issue. You are right, that should be cleaned up. — Reply to this email directly, view it on GitHub<#36838 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM4QAHGGLHPU6FUUFMZMWML4PHGYBAVCNFSM6AAAAACWIGNS3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMBXGEZDMMRUGU>. You are receiving this because you were mentioned.Message ID: ***@***.***>