Add C# Dev Kit IntelliSense guidance to VS Code tab in "Add a new field" tutorial

[Copilot]

The VS Code tab in the "Update Create.cshtml with a Rating field" section was either blank or screenshot-only across supported versions, while the VS tab had explanatory text about IntelliSense and Tag Helpers.

Changes

• new-field.md (10.0+), new-field9.md (9.0), new-field8.md (8.0) — Added explanatory text to the VS Code tab to match the VS tab's IntelliSense guidance, with a reference to the C# Dev Kit extension:

  You can copy/paste the previous "form group" and let IntelliSense help you update the fields. IntelliSense works with Tag Helpers. The C# Dev Kit extension provides IntelliSense support in Visual Studio Code.

• Fixed alt-text grammar ("existed" → "existing") in the VS Code screenshot descriptions across all three files.

• Updated ms.date in new-field.md.

Out-of-support versions (3.1, 5.0, 6.0, 7.0) are unchanged.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Empty Visual Studio Code indications</issue_title>
<issue_description>Hello, I was checking on the ASP.NET Core 3.1 docs, and I found a minor UI issue, there's an empty section if you select Visual Studio Code option after the text "Update the /Views/Movies/Create.cshtml with a Rating field"

I understand that this is because in the Visual Studio/Visual Studio Mac dialog explains that you can use IntelliSense to work with Tag Helpers.

But I believe for improving the UX the VS Code section should not be empty, it could show for example, a suggestion to the user to install the C# extension in VSCode by OmniSharp https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csharp which includes Intellisense and could help him fill the Tag Helpers.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: cca95f5e-0fe4-bbd2-fd23-13562e02f888
• Version Independent ID: c3fb9673-4da6-5eeb-08bb-6f8e7bc8e0c6
• Content: Part 8, add a new field to an ASP.NET Core MVC app
• Content Source: aspnetcore/tutorials/first-mvc-app/new-field.md
• Product: aspnet-core
• Technology: aspnetcore-tutorials
• GitHub Login: @Rick-Anderson
• Microsoft Alias: riande</issue_description>

<agent_instructions>Do not extend any fixes or changes to Razor articles, stick with the single article and related code for that article. </agent_instructions>

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

@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-02-24
Issue: 20392
Model: GitHub Copilot

---

Issue Analysis: Empty Visual Studio Code Tab Content in "Add a New Field" Tutorial

❓ Issue Validation

Status: Needs additional attention — not actionable yet as submitted
Reason: Possibly already addressed — the issue has been partially fixed across supported versions, but some older monikers still contain the original problem.

📋 Preliminary Assessment

This is an initial analysis for team review—not a final determination.

The issue was reported on 2020-10-12 against the ASP.NET Core 3.1 version of "Part 8, add a new field to an ASP.NET Core MVC app." The reporter noted that when selecting the Visual Studio Code tab after the text "Update the /Views/Movies/Create.cshtml with a Rating field," the tab was entirely empty — only containing an HTML comment <!-- This tab intentionally left blank. -->. The Visual Studio / Visual Studio for Mac tabs had IntelliSense guidance and screenshots.

Rick Anderson commented on 2020-11-02 supporting the suggestion: "@es-rene99 fantastic suggestion! @wadepickett please apply this to the RP version too."

Current State Analysis (as of 2026-02-24)

After reviewing all version-specific includes of the article, here is the fix status per moniker:

Moniker Range	File	VS Code Tab Status	Fixed?
>= aspnetcore-10.0	new-field.md L67-69	✅ Image showing VS Code form update	Yes
= aspnetcore-9.0	new-field9.md L54-56	✅ Image showing VS Code form update	Yes
= aspnetcore-8.0	new-field8.md L55-57	✅ Image showing VS Code form update	Yes
= aspnetcore-7.0	[new-field7.md L59-61](https://github.com/dotnet/AspNetCore.Docs/blob/3991a37d67aa1986ed119f05fdc5ab9be13c64d7/aspnetcore/tutorials/first-mvc-app/new-field/includes/new-field7.md#...

• Fixes Empty Visual Studio Code indications #20392

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/tutorials/first-mvc-app/new-field.md	Part 8, add a new field to an ASP.NET Core MVC app

[wadepickett]

Approved after fixes commited.