Repo sync for protected branch

docs/debugger/using-the-intellitrace-stand-alone-collector.md

@@ -1,7 +1,7 @@
 ---
 title: "Using the IntelliTrace stand-alone collector"
 description: Use the IntelliTrace stand-alone collector to collect data without installing Visual Studio and without changing the target system's environment.
-ms.date: "10/14/2023"
+ms.date: "05/18/2026"
 ms.topic: how-to
 f1_keywords:
   - "vs.historicaldebug.collectdataoutsideVS"

docs/debugger/write-better-code-with-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: Debugging techniques and tools
 description: Write better code with fewer bugs by using Visual Studio to fix exceptions and resolve errors, and make improvements to your code.
-ms.date: "1/6/2025"
+ms.date: "1/6/2026"
 ms.topic: how-to
 helpviewer_keywords:
   - "debugger"

docs/ide/copilot-agent-skills.md

@@ -44,13 +44,9 @@ Workspace skills are shared with your team through source control. Personal skil
 
 ## Create a skill
 
-<!-- This goes out in 18.6 in May and replaces the subsequent sentence.
-You can create a skill from the skills panel in Visual Studio, or manually in your file system.
--->
-
-You can create a skill manually in your file system.
+<!-- GA in 18.7, Insiders in 18.6-->
+You can create a skill from the skills panel in Visual Studio, or manually in your file system. To create a skill from the skills panel, you must have Visual Studio 2026 Insiders version 18.6 or later.
 
-<!-- This goes out in 18.6 in May
 ### Create a skill from the skills panel
 
 1. Select the **Tools** icon in the bottom-right corner of Copilot Chat to open the skills panel.
@@ -63,7 +59,6 @@ You can create a skill manually in your file system.
    :::image type="content" source="media/visualstudio/skills-create-new.png" alt-text="Screenshot that shows naming a new skill." lightbox="media/visualstudio/skills-create-new.png":::
 
 1. Visual Studio generates a skill template for you to fill in. You can use Copilot agent mode to help you complete the template.
--->
 
 ### Create a skill manually
 

docs/javascript/unit-testing-javascript-with-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: "Unit testing JavaScript and TypeScript"
 description: Explore unit testing support in Visual Studio for JavaScript and TypeScript code by using the Node.js Tools for Visual Studio.
-ms.date: "8/6/2025"
+ms.date: "05/18/2026"
 ms.topic: "how-to"
 ms.devlang: javascript
 author: "mikejo5000"

docs/modeling/modeling-sdk-for-visual-studio-domain-specific-languages.md

@@ -3,7 +3,7 @@ title: Use the Modeling SDK for Visual Studio
 description: Use the Modeling SDK for Visual Studio to create powerful model-based development tools that integrate into Visual Studio.
 titleSuffix: ''
 ms.date: 11/04/2016
-ms.topic: conceptual
+ms.topic: article
 helpviewer_keywords:
 - Domain-Specific Language Tools
 - Domain-Specific Language

docs/profiling/dotnet-counters-tool.md

@@ -1,7 +1,7 @@
 ---
 title: "Visualize dotnet counters"
 description: Use the .NET Counters tool in the Visual Studio Performance Profiler to visualize dotnet counters over time and better understand your data.
-ms.date: "02/28/2025"
+ms.date: 05/15/2026
 ms.topic: how-to
 helpviewer_keywords:
   - "dotnet, counters, profiling"
@@ -30,27 +30,57 @@ For additional information on learning to use the .NET Counters tool effectively
 
 1. Open the Performance Profiler (**Alt + F2** or **Debug -> Performance Profiler**) in Visual Studio.
 
-2. Select the **.NET Counters** check box.
+1. Select the **.NET Counters** check box.
 
-   :::image type="content" source="../profiling/media/dotnet-counters-tool-selected.png" alt-text="Counters tool selected.":::
+   ::: moniker range="visualstudio"
 
-3. Click the **Start** button to run the tool.
+   :::image type="content" source="media/visualstudio/dotnet-counters-tool-selected.png" alt-text="Screenshot of the Counters tool in Visual Studio selected.":::
+
+   ::: moniker-end
+
+   ::: moniker range="vs-2022"
+
+   :::image type="content" source="media/dotnet-counters-tool-selected.png" alt-text="Screenshot of the Counters tool selected.":::
+
+   ::: moniker-end
+
+1. Click the **Start** button to run the tool.
 
 For more information on how to optimize tool performance, see [Optimizing Profiler settings](../profiling/optimize-profiler-settings.md).
 
 ## Understand your data
 
 While the tool is initially collecting data, you can see the live values of [dotnet counters](/dotnet/core/diagnostics/dotnet-counters).
 
-:::image type="content" source="../profiling/media/dotnet-counters-tool-collecting.png" alt-text=".NET Counter tool collecting.":::
+::: moniker range="visualstudio"
+
+:::image type="content" source="media/visualstudio/dotnet-counters-tool-collecting.png" alt-text="Screenshot of the live values collected by the dotnet Counter tool in Visual Studio.":::
+
+::: moniker-end
+
+::: moniker range="vs-2022"
+
+:::image type="content" source="media/dotnet-counters-tool-collecting.png" alt-text="Screenshot of the dotnet Counter tool collecting data.":::
+
+::: moniker-end
 
 You can also view graphs of the counters by selecting the checkbox next to the counter names. You can display the graphs of multiple counters at a time.
 
 Once you are done exercising your app and collecting data, you can stop collection for an even more detailed report. To do this, press the **Stop Collection** button.
 
 Once the report loads, you should see a finalized report similar to the one shown below.
 
-:::image type="content" source="../profiling/media/dotnet-counters-tool-report.png" alt-text=".NET Counter tool report.":::
+::: moniker range="visualstudio"
+
+:::image type="content" source="media/visualstudio/dotnet-counters-tool-report.png" alt-text="Screenshot of the Counter tool final report in Visual Studio.":::
+
+::: moniker-end
+
+::: moniker range="vs-2022"
+
+:::image type="content" source="media/dotnet-counters-tool-report.png" alt-text="Screenshot of the Counter tool final report.":::
+
+::: moniker-end
 
 The report shows you the following values:
 
@@ -60,11 +90,31 @@ The report shows you the following values:
 
 You can filter or add columns in the table by right clicking the column headings and selecting a heading.
 
-:::image type="content" source="../profiling/media/dotnet-counters-tool-columns.png" alt-text=".NET Counter tool columns.":::
+::: moniker range="visualstudio"
+
+:::image type="content" source="media/visualstudio/dotnet-counters-tool-columns.png" alt-text="Screenshot of the Counter tool columns in Visual Studio.":::
+
+::: moniker-end
+
+::: moniker range="vs-2022"
+
+:::image type="content" source="media/dotnet-counters-tool-columns.png" alt-text="Screenshot of the Counter tool columns.":::
+
+::: moniker-end
 
 You can also view graphs in the detailed report by selecting the checkboxes next to counters. The data in the tables represents the values of the entire duration of your collected trace by default. To filter down the data to a specific time range, click and drag on the graphs.
 
-:::image type="content" source="../profiling/media/dotnet-counters-tool-time-filtering.png" alt-text=".NET Counters tool time filtering.":::
+::: moniker range="visualstudio"
+
+:::image type="content" source="media/visualstudio/dotnet-counters-tool-time-filtering.png" alt-text="Screenshot of the Counter tool time filtering in Visual Studio.":::
+
+::: moniker-end
+
+::: moniker range="vs-2022"
+
+:::image type="content" source="media/dotnet-counters-tool-time-filtering.png" alt-text="Screenshot of the Counter tool time filtering.":::
+
+::: moniker-end
 
 The table updates to relevant values for the time selected in the graphs. Use the **Clear Selection** button to reset the selected time range to the entire trace.
 

docs/test/isolating-code-under-test-with-microsoft-fakes.md

@@ -1,7 +1,7 @@
 ---
 title: Isolating Code Under Test with Microsoft Fakes
 description: Learn how Microsoft Fakes helps you isolate the code you are testing by replacing other parts of the application with stubs or shims.
-ms.date: 05/23/2023
+ms.date: 05/18/2026
 ms.topic: how-to
 ms.author: mikejo
 ms.manager:  aajohn
@@ -21,7 +21,7 @@ The benefit of this approach is that it allows you to focus on testing the speci
 
 - Visual Studio Enterprise
 - A .NET Framework project
-- .NET Core, .NET 5.0 or later, and SDK-style project support previewed in Visual Studio 2019 Update 6, and is enabled by default in Update 8. For more information, see [Microsoft Fakes for .NET Core and SDK-style projects](/visualstudio/releases/2019/release-notes#microsoft-fakes-for-net-core-and-sdk-style-projects).
+- .NET Core, .NET 5.0 or later, and SDK-style project support in Visual Studio 2019 and later. For more information, see [Microsoft Fakes for .NET Core and SDK-style projects](/visualstudio/releases/2019/release-notes#microsoft-fakes-for-net-core-and-sdk-style-projects).
 
 > [!NOTE]
 > Profiling with Visual Studio isn't available for tests that use Microsoft Fakes.

mac/docfx.json

@@ -109,7 +109,7 @@
       "extendBreadcrumb": true,
       "manager": "dominicn",
       "titleSuffix": "Visual Studio for Mac",
-      "ms.topic": "conceptual",
+      "ms.topic": "article",
       "audience": "developer",
       "ms.service": "visual-studio-mac",
       "ms.subservice": "ide",