Merge pull request #11057 from MicrosoftDocs/main638935744780602424sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/debugger/debug-with-copilot.md

@@ -2,7 +2,7 @@
 title: Debug with GitHub Copilot
 description: Use Copilot to help debug your apps and provide performance insights.
 ms.date: 9/12/2025
-ms.update-cycle: 180-days
+ms.update-cycle: 90-days
 ms.topic: how-to
 dev_langs: 
   - CSharp

docs/debugger/getting-started-with-the-debugger-cpp.md

@@ -11,6 +11,7 @@ helpviewer_keywords:
 author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
+ms.update-cycle: 90-days
 
 #customer intent: As a developer, I want to use Visual Studio debugger features like stepping through my application code, viewing the call stack, setting command-line arguments, and inspecting data values.
 ---

docs/get-started/csharp/tutorial-debugger.md

@@ -11,6 +11,7 @@ helpviewer_keywords:
 author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
+ms.update-cycle: 90-days
 ---
 # Tutorial: Learn to debug C# code using Visual Studio
 

docs/javascript/tutorial-asp-net-core-with-angular.md

@@ -12,6 +12,7 @@ dev_langs:
   - JavaScript
 monikerRange: '>= vs-2022'
 ms.custom: sfi-image-nochange
+ms.update-cycle: 90-days
 ---
 # Tutorial: Create an ASP.NET Core app with Angular in Visual Studio
 

docs/javascript/tutorial-asp-net-core-with-react.md

@@ -11,6 +11,7 @@ ms.subservice: javascript-typescript
 dev_langs:
   - JavaScript
 monikerRange: '>= vs-2022'
+ms.update-cycle: 90-days
 ---
 # Tutorial: Create an ASP.NET Core app with React in Visual Studio
 

docs/profiling/beginners-guide-to-performance-profiling.md

@@ -12,6 +12,7 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: debug-diagnostics
+ms.update-cycle: 90-days
 ---
 
 # Measure application performance by analyzing CPU utilization (C#, Visual Basic, C++, F#)

docs/profiling/media/visualstudio/benchmark-dotnet-template.png

@@ -7,6 +7,7 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: debug-diagnostics
+ms.update-cycle: 90-days
 ---
 # Measure memory usage in Visual Studio (C#, Visual Basic, C++, F#)
 

docs/profiling/memory-usage.md

@@ -2,7 +2,7 @@
 title: Profile with GitHub Copilot
 description: Use the Copilot Profiler Agent in Visual Studio to collect CPU and memory traces and get AI-driven performance insights and fixes.
 ms.date: 9/2/2025
-ms.update-cycle: 180-days
+ms.update-cycle: 90-days
 ms.topic: how-to
 dev_langs:
   - CSharp

docs/profiling/profile-with-copilot-agent.md

@@ -1,7 +1,7 @@
 ---
 title: "Analyze BenchmarkDotNet data in Visual Studio"
 description: Learn how to profile console apps using BenchmarkDotNet.
-ms.date: 01/27/2025
+ms.date: 09/15/2025
 ms.topic: conceptual
 dev_langs:
   - "CSharp"
@@ -40,11 +40,28 @@ Each diagnoser generates performance data related to that diagnoser. For example
   - [BenchmarkDotNET](https://www.nuget.org/packages/BenchmarkDotNet/)
   - [Microsoft.VisualStudio.DiagnosticsHub.BenchmarkDotNetDiagnosers](https://www.nuget.org/packages/Microsoft.VisualStudio.DiagnosticsHub.BenchmarkDotNetDiagnosers)
 
-## Collect Benchmark.NET data
+  ::: moniker range=">=visualstudio"
+  If you use the Benchmark project template, these NuGet packages are present when you create the project.
+  ::: moniker-end
+
+## Create your project
+
+::: moniker range=">=visualstudio"
+The benchmark functions must be added to a .NET console application. These functions can be wrapper functions that reference other project types.
+
+You can either create a console project and add BenchmarkDotNet support manually, or use the **Benchmark Project** template. Some of the steps described in this article are required only when you manually add BenchmarkDotNet support.
 
-1. Create a console project.
+The **Benchmark Project** template generates a fully integrated BenchmarkDotNet project with built-in support for CPU Usage profiling and Copilot insights. To use the template, select **Profiling** from the project types list when you create a new project, and then choose **Benchmark Project**.
 
-   The benchmark functions must be added to a .NET console application. These functions can be wrapper functions that reference other project types. 
+![Screenshot of BenchmarkDotNet template in Visual Studio.](../profiling/media/visualstudio/benchmark-dotnet-template.png) 
+::: moniker-end
+::: moniker range="vs-2022"
+Create a console project.
+
+The benchmark functions must be added to a .NET console application. These functions can be wrapper functions that reference other project types. 
+::: moniker-end
+
+## Collect Benchmark.NET data
 
 1. Set your build to a Release build instead of a Debug build.
 
@@ -54,6 +71,10 @@ Each diagnoser generates performance data related to that diagnoser. For example
 
    For example, you can use the following code for the CPUUsageDiagnoser.
 
+   ::: moniker range=">=visualstudio"
+   If you're using the **Benchmark Project** template, sample code is already provided in the template. If you're manually adding BenchmarkDotNet support, you can use the following example code.
+   ::: moniker-end
+
     ```csharp
     using System;
     using System.Security.Cryptography;