Snap main to release vs code

.azuredevops/dependabot.yml

@@ -0,0 +1,5 @@
+version: 2
+
+# Disabling dependabot on Azure DevOps as this is a mirrored repo. Updates should go through github.
+enable-campaigned-updates: false
+enable-security-updates: false

.devcontainer/devcontainer.json

@@ -39,7 +39,7 @@
         "omnisharp.useModernNet": true,
         "omnisharp.enableAsyncCompletion": true,
         // ms-dotnettools.csdevkit settings
-        "dotnet.defaultSolution": "Razor.sln",
+        "dotnet.defaultSolution": "Razor.slnx",
         // ms-vscode.powershell settings
         "powershell.promptToUpdatePowerShell": false,
         "powershell.integratedConsole.showOnStartup": false,

.editorconfig

@@ -16,7 +16,7 @@ indent_size = 4
 insert_final_newline = true
 charset = utf-8-bom
 
-file_header_template = Copyright (c) .NET Foundation. All rights reserved.\nLicensed under the MIT license. See License.txt in the project root for license information.
+file_header_template = Licensed to the .NET Foundation under one or more agreements.\nThe .NET Foundation licenses this file to you under the MIT license.
 
 # Xml project files
 [*.{csproj,vbproj,vcxproj,vcxproj.filters,proj,projitems,shproj}]
@@ -226,3 +226,10 @@ dotnet_style_prefer_inferred_tuple_names = true:suggestion
 dotnet_style_prefer_inferred_anonymous_type_member_names = true:suggestion
 dotnet_style_operator_placement_when_wrapping = beginning_of_line
 dotnet_style_prefer_compound_assignment = true:suggestion
+
+# IDE0036: Order modifiers
+csharp_preferred_modifier_order = public,private,protected,internal,static,extern,new,virtual,abstract,sealed,override,readonly,unsafe,volatile,async:suggestion
+dotnet_diagnostic.IDE0036.severity = warning
+
+# CA1052: Static holder types should be Static or NotInheritable
+dotnet_diagnostic.CA1052.severity = warning

.github/CODEOWNERS

@@ -1,15 +1,13 @@
 # Users referenced in this file will automatically be requested as reviewers for PRs that modify the given paths.
 # See https://help.github.com/articles/about-code-owners/
 
-/global.json                                   @dotnet/razor-tooling @dotnet/razor-compiler
-/azure-pipelines.yml                           @dotnet/razor-tooling @dotnet/razor-compiler
-/eng/                                          @dotnet/razor-tooling @dotnet/razor-compiler
+/global.json                                   @dotnet/razor-tooling
+/azure-pipelines.yml                           @dotnet/razor-tooling
+/eng/                                          @dotnet/razor-tooling
 /eng/targets/Services.props                    @dotnet/razor-tooling
-/eng/common/                                   @dotnet/razor-tooling @dotnet/razor-compiler
-/eng/Versions.props                            @dotnet/razor-tooling @dotnet/razor-compiler
-/eng/Version.Details.xml                       @dotnet/razor-tooling @dotnet/razor-compiler
-/eng/DotNetBuild.props                         @dotnet/product-construction
-/eng/SourceBuild*                              @dotnet/source-build
+/eng/common/                                   @dotnet/razor-tooling
+/eng/Versions.props                            @dotnet/razor-tooling
+/eng/Version.Details.xml                       @dotnet/razor-tooling
 /src/Razor                                     @dotnet/razor-tooling
-/src/Compiler                                  @dotnet/razor-compiler
-/src/Shared                                    @dotnet/razor-tooling @dotnet/razor-compiler
+/src/Compiler                                  @dotnet/razor-tooling
+/src/Shared                                    @dotnet/razor-tooling

.github/copilot-instructions.md

@@ -0,0 +1,51 @@
+# GitHub Copilot Instructions for ASP.NET Core Razor
+
+## Critical Rules
+
+- **Build**: Use `build.cmd` (Windows) or `./build.sh` (Linux/Mac). NEVER use `dotnet build` directly.
+- **Test**: Use `build.cmd -test` or target a specific project with `dotnet test path/to/Project.csproj`. NEVER run `dotnet test` at the repo root — it includes Playwright integration tests that require VS Code and waste significant time.
+- **Build wrappers**: Be careful passing `-projects` through `build.cmd`/PowerShell wrappers. Do not pass a semicolon-delimited project list through a nested PowerShell command invocation, because PowerShell can treat `;` as a statement separator and open `.csproj` files in Visual Studio. Prefer a single project at a time, or invoke the underlying script in a way that preserves the full `-projects` value as one argument.
+- **Processes**: NEVER kill dotnet processes by name (`Stop-Process -Name`, `taskkill /IM`). Other work may be running on the machine.
+- **Bug fixes**: Look for existing code that already handles the scenario before adding new code. The bug is more likely in existing logic than a missing feature.
+- **Helpers**: Review existing helpers (`UsingDirectiveHelper`, `AddUsingsHelper`, etc.) before writing new utility methods. Don't duplicate.
+
+## File Types
+
+- `.razor` — Blazor components. `.cshtml` — Razor views/pages (referred to as "Legacy" in the codebase).
+
+## Code Patterns
+
+- **Collections**: Use `ListPool<T>.GetPooledObject(out var list)` and `PooledArrayBuilder<T>` instead of allocating new collections. Prefer immutable collection types.
+- **Positions**: Use `GetRequiredAbsoluteIndex` for converting positions to absolute indexes.
+- **LSP conversions**: `sourceText.GetTextChange(textEdit)` converts LSP `TextEdit` → Roslyn `TextChange`. Reverse: `sourceText.GetTextEdit(change)`. Both in `LspExtensions_SourceText.cs`.
+- **RazorCodeDocument**: Immutable — every `With*` method creates a new instance passing ALL fields through the constructor. When adding a new field, thread it through every existing `With*` method. Prefer computing derived data via extension methods (e.g., `GetUnusedDirectives()`) rather than storing computed results as fields.
+- **Razor documents in Roslyn**: Stored as additional documents. Resolve via `solution.GetDocumentIdsWithFilePath(filePath)` → `solution.GetAdditionalDocument(documentId)`.
+- **Remote services**: Place the public stub method (calling `RunServiceAsync`) directly above its private implementation method.
+
+## Testing
+
+- Place `[WorkItem("url")]` on tests that track a specific issue (GitHub or DevOps URL).
+- Use `TestCode` with `[|...|]` span markers for before/after test scenarios. Access `input.Text` (cleaned) and `input.Span` (marked range).
+- Prefer raw string literals (`"""..."""`) over verbatim strings (`@"..."`).
+- Test end-user scenarios, not implementation details.
+- Verify/helper methods go at the bottom of test files. New test methods go above them.
+- New tooling tests go in `src\Razor\test\Microsoft.VisualStudioCode.RazorExtension.Test` (Cohosting architecture).
+- Integration tests using `AdditionalSyntaxTrees` for tag helper discovery must set `UseTwoPhaseCompilation => true` (see `ComponentDiscoveryIntegrationTest`).
+
+## Adding OOP Remote Services
+
+When adding a new `IRemote*Service` and `Remote*Service`:
+
+1. Interface → `src\Razor\src\Microsoft.CodeAnalysis.Razor.Workspaces\Remote\`
+2. Implementation → `src\Razor\src\Microsoft.CodeAnalysis.Remote.Razor\`
+3. Register in `RazorServices.cs` (add to `MessagePackServices` or `JsonServices`)
+4. **Add entry to `eng\targets\Services.props`**: `Include="Microsoft.VisualStudio.Razor.{ShortName}"` with `ClassName="{FullTypeName}+Factory"`
+5. Validate: `dotnet test src\Razor\test\Microsoft.CodeAnalysis.Remote.Razor.Test --filter "FullyQualifiedName~RazorServicesTest"`
+
+## VS Code Validation
+
+Run Playwright E2E tests (exception to the "no `dotnet test` at root" rule):
+```powershell
+cd src\Razor\test\Microsoft.VisualStudioCode.Razor.IntegrationTests
+dotnet test
+```

.github/policies/resourceManagement.yml

@@ -260,5 +260,36 @@ configuration:
       - addMilestone:
           milestone: Next
       description: '[PRs] Milestone tracking'
+    - if:
+      - payloadType: Issues
+      - labelAdded:
+          label: breaking-change
+      then:
+      - addReply:
+          reply: >-
+            Refer to the [.NET SDK breaking change guidelines](https://github.com/dotnet/sdk/blob/main/documentation/project-docs/breaking-change-guidelines.md#required-process-for-all-net-sdk-breaking-changes)
+      description: Add breaking change doc instructions to issue
+    - if:
+      - payloadType: Pull_Request
+      - labelAdded:
+          label: breaking-change
+      then:
+      - addLabel:
+          label: needs-breaking-change-doc-created
+      - addReply:
+          reply: >-
+            Added `needs-breaking-change-doc-created` label because this PR has the `breaking-change` label. 
+
+
+            When you commit this breaking change:
+
+
+            1. [ ] Create and link to this PR and the issue a matching issue in the dotnet/docs repo using the [breaking change documentation template](https://aka.ms/dotnet/docs/new-breaking-change-issue), then remove this `needs-breaking-change-doc-created` label.
+
+            2. [ ] Ask a committer to mail the `.NET SDK Breaking Change Notification` email list.
+
+
+            You can refer to the [.NET SDK breaking change guidelines](https://github.com/dotnet/sdk/blob/main/documentation/project-docs/breaking-change-guidelines.md)
+      description: Add breaking change instructions to PR.
 onFailure: 
 onSuccess: