Merge pull request #10577 from MicrosoftDocs/main638729319222538971sync_temp

learn-build-service-prod[bot] · web-flow · commit 0b3a1ab930ba · 2025-01-20T01:05:34.000Z
For protected branch, push strategy should use PR and merge to target branch method to work around git push error
diff --git a/docs/debugger/using-breakpoints.md b/docs/debugger/using-breakpoints.md
@@ -1,5 +1,5 @@
 ---
-title: Use the right type of breakpoints
+title: Use the right type of breakpoint
 description: Learn about the different types of breakpoints, one of the most important debugging techniques. The article covers breakpoint actions, tracepoints, conditions, and much more.
 ms.date: 08/13/2024
 ms.topic: how-to
@@ -29,6 +29,8 @@ This article shows how to use different types of breakpoints in Visual Studio to
 
 If you're unfamiliar with using breakpoints in Visual Studio, see [Get started with breakpoints](get-started-with-breakpoints.md) before going through this article.
 
+For the best experience with this documentation, choose your preferred development language or runtime from the list at the top of the article.
+
 ::: zone pivot="programming-language-dotnet,programming-language-dotnetf,programming-language-cpp,programming-language-all"
 ## Scenarios
 
diff --git a/docs/modeling/analyze-and-model-your-architecture.md b/docs/modeling/analyze-and-model-your-architecture.md
@@ -74,6 +74,9 @@ Learn more:
 
 ## <a name="VersionSupport"></a> Edition support for architecture and modeling tools
 
+> [!NOTE]
+> Architecture tools are not supported on ARM64 Visual Studio.
+
 Visual Studio is available in several editions. Not all of these provide support for the architecture and modeling tools. The following table shows the availability of each tool.
 
 |**Feature**|**Enterprise edition**|**Professional edition**|**Community edition**|
diff --git a/docs/profiling/memory-usage-without-debugging2.md b/docs/profiling/memory-usage-without-debugging2.md
@@ -12,13 +12,17 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: debug-diagnostics
+zone_pivot_groups: programming-languages-set-two
 ---
 # Analyze memory usage in release builds (C#, Visual Basic, C++, F#)
 
 The **Memory Usage** tool monitors your app's memory use. You can use the tool to study the real-time memory effects of scenarios you're actively developing in Visual Studio. You can take detailed snapshots of the app's memory states, and compare snapshots to find the root causes of memory issues. The Memory Usage tool is supported on .NET, ASP.NET, C++, or mixed mode (.NET and native) apps.
 
 The Memory Usage tool can run [on release or debug builds](../profiling/running-profiling-tools-with-or-without-the-debugger.md). In this article, we show how to use the Memory Usage tool in the Visual Studio **Performance Profiler**, which is recommended for release builds. For information on choosing the best memory analysis tool for your needs, see [Choose a memory analysis tool](../profiling/analyze-memory-usage.md).
 
+For the best experience with this documentation, choose your preferred development language or runtime from the list at the top of the article.
+
+::: zone pivot="programming-language-dotnet,programming-language-dotnetf,programming-language-cpp"
 ## Memory Usage diagnostic sessions
 
 **To start a Memory Usage diagnostic session:**
@@ -40,6 +44,7 @@ The Memory Usage tool can run [on release or debug builds](../profiling/running-
    ::: moniker range="vs-2019"
    ![Start a Memory Usage diagnostic session.](../profiling/media/memory-usage-start-diagnostics-session.png "Start a Memory Usage diagnostic session")
    ::: moniker-end
+::: zone-end
 
 ### Monitor memory use
 
@@ -121,6 +126,7 @@ For C++, the **Objects (Diff)** column is named **Allocations (Diff)**.
 |![Step 4](../profiling/media/process-guide-4.png "Process Guide-4")|The difference between the total number of memory objects in this snapshot and the previous snapshot. Select this link to display a snapshot diff report. It’s sorted by the difference in the total count of instances of the types.|
 ::: moniker-end
 
+::: zone pivot="programming-language-dotnet,programming-language-dotnetf"
 ## Managed types reports
 
 [!INCLUDE [managed-types-report](../profiling/includes/managed-types-report.md)]
@@ -142,7 +148,9 @@ Many types in apps aren't required for app developers to investigate memory issu
 - <a name="BKMK_Just_My_Code"></a> Select **Show Just My Code** in the **Filter** dropdown to hide most instances that are generated by external code. External types belong to the operating system or framework components, or are generated by the compiler.
 
 - <a name="BKMK_Collapse_Small_Objects"></a> Select **Collapse Small Objects** in the **Filter** dropdown to hide types whose **Size (Bytes)** is less than 0.5 percent of the total memory.
+::: zone-end
 
+::: zone pivot="programming-language-cpp"
 ## Native types reports
 
 [!INCLUDE [native-types-report](../profiling/includes/native-types-report.md)]
@@ -152,6 +160,7 @@ Many types in apps aren't required for app developers to investigate memory issu
 
 [!INCLUDE [memory-usage-insights](../profiling/includes/memory-usage-insights.md)]
 ::: moniker-end
+::: zone-end
 
 ## Change (Diff) reports
 
diff --git a/docs/profiling/profiling-feature-tour.md b/docs/profiling/profiling-feature-tour.md
@@ -1,7 +1,7 @@
 ---
 title: "First look at profiling tools"
 description: Review the different diagnostic tools available in Visual Studio for profiling your C#, Visual Basic, C++, and F# applications.
-ms.date: 11/19/2024
+ms.date: 1/17/2025
 ms.topic: conceptual
 f1_keywords:
   - vs.diagnosticshub.overview
@@ -13,13 +13,16 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: debug-diagnostics
+zone_pivot_groups: programming-languages-set-two
 ---
 # First look at profiling tools (C#, Visual Basic, C++, F#)
 
 Application performance measuring tools are essential for developers who want to optimize their code and improve application performance. Visual Studio offers a range of profiling and diagnostics tools that can help you diagnose memory and CPU usage and other application-level issues. With these tools, you can accumulate performance data while you run your application. A profiler can help you make informed decisions quickly by providing a visual depiction of execution times and CPU usage for your application. In this article, we give a quick look at the most common profiling tools.
 
 For help with choosing the correct tool, or to see profiling tool support for different app types, see [Which tool should I use?](../profiling/choose-performance-tool.md) For a tutorial that shows a general approach to optimizing code using the profiling tools, see [Case study: Beginner's guide to optimizing code](../profiling/optimize-code-using-profiling-tools.md).
 
+For the best experience with this documentation, choose your preferred development language or runtime from the list at the top of the article.
+
 ## <a name="post_mortem"></a> Measure performance in release builds
 
 Tools in the Performance Profiler are intended to provide analysis for **Release** builds. In the Performance Profiler, you can collect diagnostic info while the app is running, and then examine the collected information after the app is stopped (a post-mortem analysis).
@@ -37,6 +40,7 @@ For more information on using the CPU Usage or Memory usage tool in the Performa
 
 Tools available in the Performance Profiler include:
 
+::: zone pivot="programming-language-dotnet"
 - [CPU usage](../profiling/cpu-usage.md)
 - [.NET object allocation](../profiling/dotnet-alloc-tool.md)
 - [Memory usage](../profiling/memory-usage-without-debugging2.md)
@@ -46,6 +50,22 @@ Tools available in the Performance Profiler include:
 - [.NET Counters](../profiling/dotnet-counters-tool.md)
 - [Database tool](../profiling/analyze-database.md)
 - [GPU usage](../profiling/gpu-usage.md)
+::: zone-end
+
+::: zone pivot="programming-language-dotnetf"
+- [CPU usage](../profiling/cpu-usage.md)
+- [Memory usage](../profiling/memory-usage-without-debugging2.md)
+- [Instrumentation](../profiling/instrumentation-overview.md)
+- [File I/O](../profiling/use-file-io.md)
+::: zone-end
+
+::: zone pivot="programming-language-cpp"
+- [CPU usage](../profiling/cpu-usage.md)
+- [Memory usage](../profiling/memory-usage-without-debugging2.md)
+- [Instrumentation](../profiling/instrumentation-overview.md)
+- [File I/O](../profiling/use-file-io.md)
+- [GPU usage](../profiling/gpu-usage.md)
+::: zone-end
 
 To see profiling tool support for different app types, see [Which tool should I use?](../profiling/choose-performance-tool.md).
 
@@ -80,7 +100,9 @@ Tools available in the Diagnostic Tools window or during a debugging session inc
 
 - [CPU usage](../profiling/beginners-guide-to-performance-profiling.md)
 - [Memory usage](../profiling/memory-usage.md)
+::: zone pivot="programming-language-dotnet"
 - [.NET Counters](../profiling/dotnet-counters-tool.md)
+::: zone-end
 - [PerfTips](../profiling/perftips.md)
 ::: moniker-end
 ::: moniker range="<=vs-2019"
@@ -211,6 +233,7 @@ PerfTips show the same events that also show up in the **Events** view of the Di
  > [!NOTE]
  > If you have Visual Studio Enterprise, you can also see [IntelliTrace events](../debugger/intellitrace.md) in this tab.
 
+::: zone pivot="programming-language-dotnet"
 ::: moniker range=">=vs-2022"
 ## Analyze asynchronous code (.NET)
 
@@ -219,6 +242,8 @@ The [.NET Async tool](../profiling/analyze-async.md) allows you to analyze the p
 The tool shows each async operation in a list view. You can see information such as the start time, end time, and total time for an async operation.
 
 ![.NET Async Tool Stopped](../profiling/media/vs-2022/prof-tour-async-tool.png ".NET Async Tool Stopped")
+
+This tool is supported for For .NET Core and .NET 5+ apps.
 ::: moniker-end
 ::: moniker range="vs-2019"
 ## Analyze asynchronous code (.NET)
@@ -228,24 +253,29 @@ The [.NET Async tool](../profiling/analyze-async.md) allows you to analyze the p
 The tool shows each async operation in a list view. You can see information such as the start time, end time, and total time for an async operation.
 
 ![.NET Async Tool Stopped](../profiling/media/async-tool-opened.png ".NET Async Tool Stopped")
+
+This tool is supported for For .NET Core and .NET 5+ apps.
 ::: moniker-end
 
-## Analyze database performance (.NET Core)
+## Analyze database performance (.NET)
 
-For .NET Core apps that use ADO.NET or Entity Framework Core, the [Database tool](../profiling/analyze-database.md) allows you to record the database queries that your application makes during a diagnostic session. You can then analyze information about individual queries in order to find places where your app's performance can be improved. This tool is available in the Performance Profiler. Open the Performance Profiler by choosing **Debug** > **Performance Profiler** (or **Alt + F2**).
+For .NET Core and .NET 5+ apps that use ADO.NET or Entity Framework Core, the [Database tool](../profiling/analyze-database.md) allows you to record the database queries that your application makes during a diagnostic session. You can then analyze information about individual queries in order to find places where your app's performance can be improved. This tool is available in the Performance Profiler. Open the Performance Profiler by choosing **Debug** > **Performance Profiler** (or **Alt + F2**).
 
 The tool shows each query in a list view. You can see information such as the query start time and duration.
 
 ![Allocation](./media/db-gotosource.png "Allocation")
 
-## Visualize .NET counters (.NET Core)
+## Visualize .NET counters (.NET)
 
 Starting in Visual Studio 2019 version 16.7, you can use the [.NET Counters tool](../profiling/dotnet-counters-tool.md) in Visual Studio to visualize performance counters. You can visualize counters created using [dotnet counters](/dotnet/core/diagnostics/dotnet-counters). dotnet counters supports many counters such as CPU usage and garbage collector heap size.
 
 The tool shows live values for each counter in a list view.
 
 :::image type="content" source="../profiling/media/dotnet-counters-tool-collecting.png" alt-text=".NET Counter tool collecting.":::
 
+This tool is supported for For .NET Core and .NET 5+ apps.
+::: zone-end
+
 ## Examine application events
 
 The generic [events viewer](../profiling/events-viewer.md) allows you to view the activity of your application through a list of events, such as module load, thread start, and system configurations, to help better diagnose how your application is performing right within the Visual Studio profiler. This tool is available in the Performance Profiler. Open the Performance Profiler by choosing **Debug** > **Performance Profiler** (or **Alt + F2**).
@@ -260,6 +290,7 @@ The tool shows each event in a list view. Columns provide information about each
 You can programatically create custom events that appear as icons in the timeline graphs such as the CPU utilization and memory usage timeline graphs. For more information, see [Add user marks to timeline](../profiling/add-timeline-graph-user-marks.md).
 ::: moniker-end
 
+::: zone pivot="programming-language-dotnet,programming-language-dotnetf"
 ## Analyze resource consumption (XAML)
 
 In XAML apps, such as Windows desktop WPF apps and UWP apps, you can analyze resource consumption using the Application Timeline tool. For example, you can analyze the time spent by your application preparing UI frames (layout and render), servicing network and disk requests, and in scenarios like application startup, page load, and Window resize. To use the tool, choose **Application Timeline** in the Performance Profiler, and then choose **Start**. In your app, go through the scenario with a suspected resource consumption issue, and then choose **Stop collection** to generate the report.
@@ -286,7 +317,9 @@ In your UWP apps, you can enable **UI Analysis** in the **Diagnostic Tools** win
 ::: moniker range="<=vs-2019"
 ![View UI analysis events in the diagnostic tools](../profiling/media/prof-tour-ui-analysis.png "Diagnostic Tools View UI Analysis Events")
 ::: moniker-end
+::: zone-end
 
+::: zone pivot="programming-language-cpp"
 ## Analyze GPU Usage (Direct3D)
 
 In Direct3D apps (Direct3D components must be in C++), you can examine activity on the GPU and analyze performance issues. For more information, see [GPU Usage](./gpu-usage.md). To use the tool, choose **GPU Usage** in the Performance Profiler, and then choose **Start**. In your app, go through the scenario that you're interested in profiling, and then choose **Stop collection** to generate a report.
@@ -301,6 +334,7 @@ When you select a time period in the graphs and choose **view details**, a detai
 ::: moniker-end
 
 You can also use the graphs to determine whether there are CPU bound or GPU bound performance bottlenecks.
+::: zone-end
 
 ## Analyze performance (legacy tools)
 
diff --git a/docs/zone-pivot-groups.yml b/docs/zone-pivot-groups.yml
@@ -2,7 +2,7 @@
 groups:
 - id: programming-languages-set-one
   title: Programming languages
-  prompt: Choose a supported programming language
+  prompt: Choose a programming language or runtime
   pivots:
   - id: programming-language-dotnet
     title: .NET
@@ -11,11 +11,23 @@ groups:
   - id: programming-language-cpp
     title: C++
   - id: programming-language-all
-    title: All languages
+    title: Other languages
 # Notice how the ids, titles, and prompts are
 # consistent and in order.
-# Note: Set two is not used currently, but is present as an example set two.
 - id: programming-languages-set-two
+  title: Programming languages
+  prompt: Choose a programming language or runtime
+  pivots:
+  - id: programming-language-dotnet
+    title: .NET
+  - id: programming-language-dotnetf
+    title: .NET Framework
+  - id: programming-language-cpp
+    title: C++
+# Notice how the ids, titles, and prompts are
+# consistent and in order.
+# Note: This set is not used currently, but is present as an example.
+- id: programming-languages-set-three
   title: Programming languages
   prompt: Choose a supported programming language
   pivots:
