Merge to Live

.github/CODEOWNERS

@@ -0,0 +1,43 @@
+# Lines starting with '#' are comments.
+# Each line is a file pattern followed by one or more owners.
+
+# More details are here: https://help.github.com/articles/about-codeowners/
+# Initial experience with this file was not all positive, so most lines are currently commented out.
+# It will be easy to give it another trial should we decide to do that.
+
+# The '*' pattern is global owners.
+
+# *     
+
+# .github/  
+
+# Order is important. The last matching pattern has the most precedence.
+
+/aspnetcore/blazor/ @guardrex
+# /aspnetcore/breadcrumb/ 
+# /aspnetcore/client-side/ 
+# /aspnetcore/common/ 
+# /aspnetcore/data/ 
+# /aspnetcore/diagnostics/ @Rick-Anderson
+# /aspnetcore/fundamentals/ @tdykstra
+# /aspnetcore/getting-started/ 
+# /aspnetcore/grpc/ @wadepickett
+# /aspnetcore/host-and-deploy/ @Rick-Anderson
+# /aspnetcore/includes/ 
+# /aspnetcore/log-mon/ @Rick-Anderson
+# /aspnetcore/migration/ @Rick-Anderson
+# /aspnetcore/mobile/ 
+# /aspnetcore/mvc/ 
+/aspnetcore/performance/caching/ @tdykstra 
+# /aspnetcore/razor-pages/ 
+# /aspnetcore/release-notes/ 
+# /aspnetcore/security/ @Rick-Anderson
+# /aspnetcore/signalr/ @wadepickett
+# /aspnetcore/test/ 
+# /aspnetcore/tutorials/ @wadepickett
+# /aspnetcore/web-api/ @wadepickett @Rick-Anderson
+# /aspnetcore/whats-new/ @Rick-Anderson
+/client-side/dotnet-interop/index.md @guardrex
+/client-side/dotnet-interop/wasm-browser-app.md @guardrex
+/mvc/views/tag-helpers/built-in/component-tag-helper.md @guardrex
+/mvc/views/tag-helpers/built-in/persist-component-state.md @guardrex

.github/ISSUE_TEMPLATE/blank-issue.md

@@ -0,0 +1,24 @@
+---
+name: Blank issue
+about: Create an issue to help us improve
+---
+
+# Before you open an issue
+
+If the issue is with an ASP.NET Core document:
+
+* Do **not** open a new issue using this form.
+* Open the issue using the **Open a documentation issue** link and feedback form at the bottom of the article. 
+
+Using the **Open a documentation issue** link and form to open an issue adds article metadata for tracking, which indicates the article that you're commenting on and pings the author for a faster response.
+
+If the issue is:
+
+* A simple typo or similar correction, you can submit a PR. See the Contributor Guide for instructions: https://docs.microsoft.com/contribute/#quick-edits-to-existing-documents
+* A general support question, consider asking on a support forum:
+  * Stack Overflow: https://stackoverflow.com/questions/tagged/asp.net-core
+  * ASP.NET Core Slack: https://aspnetcore.slack.com/join/shared_invite/zt-1mv5487zb-EOZxJ1iqb0A0ajowEbxByQ#/shared-invite/email
+  * ASP.NET Gitter: https://gitter.im/aspnet/Home
+* A site design concern, create an issue at MicrosoftDocs/Feedback: https://github.com/MicrosoftDocs/Feedback/issues/new/choose
+* A problem completing a tutorial, compare your code with the completed sample.
+* A duplicate of an open or closed issue, leave a comment on that issue.

.github/ISSUE_TEMPLATE/customer-feedback.yml

@@ -0,0 +1,60 @@
+name: Learn feedback control.
+description: |
+  ⛔ This template is hooked into the feedback control on the bottom of every page on the live site. It automatically fills in several fields for you. Don't use for other purposes. ⛔
+body:
+  - type: markdown
+    attributes:
+      value: "## Issue information"
+  - type: markdown
+    attributes:
+      value: Describe the issue in the following text box. Add as much detail as needed to help us resolve the issue.
+  - type: textarea
+    id: feedback
+    validations:
+      required: true
+    attributes:
+      label: Description
+  - type: markdown
+    attributes:
+      value: "## 🚧 Article information 🚧"
+  - type: markdown
+    attributes:
+      value: "The following fields are automatically filled in. ***Don't edit them.*** Doing so will disconnect your issue from the affected article. To find other issues for this article, search for the Document ID."
+  - type: input
+    id: pageUrl
+    validations:
+      required: true
+    attributes:
+      label: Page URL
+  - type: input
+    id: contentSourceUrl
+    validations:
+      required: true
+    attributes:
+      label: Content source URL
+  - type: input
+    id: documentVersionIndependentId
+    validations:
+      required: true
+    attributes:
+      label: Document ID
+  - type: input
+    id: platformId
+    validations:
+      required: true
+    attributes:
+      label: Platform Id
+  - type: input
+    id: author
+    validations:
+      required: true
+    attributes:
+      label: Article author
+  - type: textarea
+    id: metadata
+    validations:
+      required: false
+    attributes:
+      label: Metadata
+      description: >-
+        Documentation metadata will be applied here

.github/ISSUE_TEMPLATE/doc-issue.md

@@ -8,18 +8,18 @@ about: Create an issue to help us improve
 If the issue is with an ASP.NET Core document:
 
 * Do **not** open a new issue using this form.
-* Open the issue with the **This page** button and form at the bottom of the document's page.
+* Open the issue using the **Open a documentation issue** link and feedback form at the bottom of the article. 
 
-Using the **This page** button and form to open an issue:
-
-* Adds article metadata for tracking, which indicates the article that you're commenting on.
-* Automatically notifies the article's author about your issue.
+Using the **Open a documentation issue** link and form to open an issue adds article metadata for tracking, which indicates the article that you're commenting on.
 
 If the issue is:
 
-* A simple typo or similar correction, you can submit a PR. See [the contributor guide](https://docs.microsoft.com/contribute/#quick-edits-to-existing-documents) for instructions.
-* A general support question, consider asking on a support forum site.
-* A site design concern, create an issue at [MicrosoftDocs/Feedback](https://github.com/MicrosoftDocs/Feedback/issues/new/choose).
+* A simple typo or similar correction, you can submit a PR. See the Contributor Guide for instructions: https://docs.microsoft.com/contribute/#quick-edits-to-existing-documents
+* A general support question, consider asking on a support forum:
+  * Stack Overflow: https://stackoverflow.com/questions/tagged/asp.net-core
+  * ASP.NET Core Slack: https://aspnetcore.slack.com/join/shared_invite/zt-1mv5487zb-EOZxJ1iqb0A0ajowEbxByQ#/shared-invite/email
+  * ASP.NET Gitter: https://gitter.im/aspnet/Home
+* A site design concern, create an issue at MicrosoftDocs/Feedback: https://github.com/MicrosoftDocs/Feedback/issues/new/choose
 * A problem completing a tutorial, compare your code with the completed sample.
 * A duplicate of an open or closed issue, leave a comment on that issue.
 
@@ -36,7 +36,7 @@ Check the .NET target framework(s) being used, and include the version number(s)
 * [ ] .NET Framework
 * [ ] .NET Standard
 
-If using the .NET Core SDK, include `dotnet --info` output. If using .NET Framework without the .NET Core SDK, include info from Visual Studio's **Help** > **About Microsoft Visual Studio** dialog.
+If using the .NET SDK, include `dotnet --info` output. If using .NET Framework without the .NET SDK, include info from Visual Studio's **Help** > **About Microsoft Visual Studio** dialog.
 
 <details>
 <summary><strong>dotnet --info output</strong> or <strong>About VS info</strong></summary>

.github/ISSUE_TEMPLATE/doc-request.md

@@ -5,12 +5,12 @@ about: Request a new topic to help us improve
 
 **Help us make content visible**
 
-- Tell us what search terms you used and how you searched docs.
-- Tell us what docs you found that didn't address your concern.
+* Tell us what search terms you used and how you searched docs.
+* Tell us what docs you found that didn't address your concern.
 
 **Describe the new topic**
 
-- Explain why this topic is needed.
-- Suggest a location in the Table of Contents.
-- Write an abstract. In one **short** paragraph, describe what this topic will cover.
-- Create an outline for the new topic. We'll help review the outline and approve it before anyone writes a topic.
+* Explain why this topic is needed.
+* Suggest a location in the Table of Contents.
+* Write an abstract. In one **short** paragraph, describe what this topic will cover.
+* Create an outline for the new topic. We'll help review the outline and approve it before anyone writes a topic.

.github/copilot-code-instructions.md

@@ -0,0 +1,108 @@
+---
+author: tdykstra
+ms.author: wpickett
+ms.date: 09-22-2025
+---
+
+# Copilot Code Instructions for `dotnet/AspNetCore.Docs`
+
+## Introduction
+This document contains code-specific instructions for GitHub Copilot when assisting with the `dotnet/AspNetCore.Docs` repository. For general instructions and documentation guidelines, please refer to the [copilot-instructions.md](./copilot-instructions.md) file.
+
+## Code-Related Guidelines
+
+### 1. Code Snippets
+- [ ] For code snippets longer than 6 lines:
+  - [ ] Create a subfolder named after the document the snippet supports.
+  - [ ] Create a `snippets` folder inside that subfolder.
+  - [ ] For the code file:
+     - [ ] If the snippet is not version-specific, place the code in a file with the appropriate extension (for example, `.cs` for C#) in the `snippets` folder.
+     - [ ] If the snippet is version-specific:
+        - [ ] Create a subfolder inside the `snippets` folder named for the version (for example, `9.0` for .NET 9 or ASP.NET Core 9).
+        - [ ] Place the code in a file with the correct extension inside the version subfolder.
+        - [ ] Add a project file (`.csproj`) to the version subfolder targeting the matching .NET version, if necessary to run or build the snippet.
+- [ ] Reference snippets using triple-colon syntax:
+  - [ ] **Use file-relative paths** for snippets located in the same file as the articles that refer to it.
+    ```
+    :::code language="csharp" source="../snippets/my-doc/Program.cs":::
+    ```
+  - [ ] **Use repository root-relative paths** for shared snippets:
+    ```
+    :::code language="csharp" source="~/tutorials/min-web-api/samples/9.x/todoGroup/TodoDb.cs":::
+    ```
+- [ ] For longer snippets, highlight specific lines:
+  ```
+  :::code language="csharp" source="~/path/to/file.cs" range="5-10" highlight="2-3":::
+  ```
+- [ ] Use the latest, non-preview C# coding patterns in non-preview code examples
+- [ ] Use the latest preview C# coding patterns in preview code examples
+- [ ] Use the following language code and indentation standards for markdown code blocks or the `language` attribute of code snippets:
+
+  Content of the snippet | Language code | Indentation in spaces
+  :--------------------: | :-----------: | :-------------------:
+  C#                     | csharp        | 4
+  HTML                   | html          | 4
+  CSS                    | css           | 4
+  JavaScript             | javascript    | 2 spaces (use 4 spaces for line continuation)
+  XML                    | xml           | 2
+  JSON                   | json          | 2
+  Console                | console       | 2
+  Text                   | -             | 2
+
+- [ ] Code Snippet Folder Structure Requirements:
+  - [ ] For code snippets longer than 6 lines, create proper folder structure: article-name/snippets/version/filename.cs (e.g., cookie/snippets/6.0/Program.cs)
+  - [ ] Create version-specific subfolders: 3.x, 6.0, 8.0, 9.0, etc.
+  - [ ] Use file-relative paths for snippets in same article folder
+  - [ ] Use repository root-relative paths (~/) for shared snippets
+- [ ] Code Snippet Markers in .cs Files - CRITICAL:
+  - [ ] NEVER use #region snippet_name and #endregion syntax in .cs files
+  - [ ] ALWAYS use // <snippet_name> and // </snippet_name> format (all lowercase)
+  - [ ] Examples of correct .cs file snippet markers:
+    ```csharp
+    // <snippet_policy>
+    var cookiePolicyOptions = new CookiePolicyOptions
+    {
+        MinimumSameSitePolicy = SameSiteMode.Strict,
+    };
+    app.UseCookiePolicy(cookiePolicyOptions);
+    // </snippet_policy>
+    ```
+  - [ ] INCORRECT format to avoid:
+    ```csharp
+    #region snippet_policy
+    // code here
+    #endregion
+    ```
+- [ ] Code Comments and Localization:
+  - [ ] NEVER add explanatory code comments like `// Configure cookie policy options` in .cs snippet files
+  - [ ] NEVER add comments like `// Add Cookie Policy Middleware` - these prevent proper localization
+  - [ ] Rely on markdown prose before/after code snippets for explanations instead of inline comments
+  - [ ] Only keep comments that are essential to the code's functionality
+- [ ] Common Syntax Errors to Avoid:
+  - [ ] Using `range="5-10"` instead of `id="snippet_name"`
+  - [ ] Using `name="snippet_name"` instead of `id="snippet_name"`
+  - [ ] Mixing old [!code-csharp[]] syntax with new triple-colon syntax.  Use triple-colon syntax.
+  - [ ] Using absolute line numbers in highlight="" instead of relative to snippet
+  - [ ] Using #region/#endregion in .cs files instead of // <snippet_name> format
+- [ ] Version-Specific Considerations:
+  - [ ] Create separate snippet files for different .NET versions (3.x, 6.0, 8.0, 9.0+)
+  - [ ] Ensure examples use appropriate syntax for the target version
+  - [ ] Reference the correct version-specific snippet file in markdown
+
+### 2. Code Build and Testing Requirements
+- [ ] Ensure all code samples build successfully against the targeted .NET version
+- [ ] Include necessary using statements in code samples
+- [ ] When you're assigned an issue involving code changes, after you've completed your work and the workflows (status checks) have run, ensure there are no build warnings under the OpenPublishing.Build status check
+- [ ] Use `#nullable enable` in C# code samples that use nullable reference types
+- [ ] For Minimal API examples, use the latest patterns including group-based routing where appropriate
+- [ ] For code samples targeting preview versions:
+  - [ ] Clearly indicate in comments or surrounding documentation that the code targets a preview version
+  - [ ] Provide fallback examples for current stable versions when possible
+
+### 3. ASP.NET Core Code-Specific Guidelines
+- [ ] Use the latest supported version for examples unless otherwise specified
+- [ ] Include differences between Minimal API and controller-based approaches when relevant
+- [ ] For middleware content and examples, use the middleware class approach
+- [ ] Code examples should be concise and focused on demonstrating a specific concept
+- [ ] Include error handling in code examples where appropriate
+- [ ] Ensure all code is accessible and follows best practices for ASP.NET Core applications