Updates

Author: guardrex

aspnetcore/blazor/performance/app-download-size.md

@@ -5,7 +5,7 @@ description: Tips for reducing app download size in ASP.NET Core Blazor apps and
 monikerRange: '>= aspnetcore-3.1'
 ms.author: riande
 ms.custom: mvc
-ms.date: 04/16/2025
+ms.date: 04/30/2025
 uid: blazor/performance/app-download-size
 ---
 # ASP.NET Core Blazor app download size performance best practices

aspnetcore/blazor/performance/developer-tools-profiling.md renamed to aspnetcore/blazor/performance/browser-developer-tools-profiling.md

@@ -1,22 +1,22 @@
 ---
-title: ASP.NET Core Blazor WebAssembly developer tools performance profiling and diagnostic counters
+title: ASP.NET Core Blazor WebAssembly browser developer tools diagnostic profiling
 author: guardrex
-description: Learn about developer tools performance profiling and diagnostic counters in ASP.NET Core Blazor WebAssembly apps.
+description: Learn about browser developer tools diagnostic profiling for ASP.NET Core Blazor WebAssembly apps.
 monikerRange: '>= aspnetcore-10.0'
 ms.author: riande
 ms.custom: mvc
-ms.date: 04/29/2025
-uid: blazor/performance/developer-tools-profiling
+ms.date: 04/30/2025
+uid: blazor/performance/browser-developer-tools
 ---
-# ASP.NET Core Blazor WebAssembly developer tools performance profiling and diagnostic counters
+# ASP.NET Core Blazor WebAssembly browser developer tools diagnostic profiling
 
 <!-- UPDATE 10.0 - Activate ...
 
 [!INCLUDE[](~/includes/not-latest-version.md)]
 
 -->
 
-This article describes developer tools performance profiling tools and diagnostic counters for Blazor WebAssembly apps.
+This article describes browser developer tools diagnostic profiling tools for Blazor WebAssembly apps.
 
 ## Prerequisite
 
@@ -28,9 +28,9 @@ dotnet workload install wasm-tools
 
 ## Browser developer tools
 
-App code can be manually profiled using the performance profiler in a browser's developer tools console.
+App code can be manually profiled using the diagnostic profiler in a browser's developer tools console.
 
-Built-in performance counters are available to track:
+Built-in diagnostic counters are available to track:
 
 * [Ahead-of-time (AOT) compilation](xref:blazor/tooling/webassembly#ahead-of-time-aot-compilation)
 * Code interpolation
@@ -47,21 +47,25 @@ Property | Default | Set value to&hellip; | Description
 `<WasmNativeDebugSymbols>` | `true` | `true` | Controls building with native debug symbols.
 `<WasmBuildNative>` | `false` | `true` | Controls building the native executable.
 
-Enabling profilers has negative size and performance impact, so don't publish an app for production with profilers enabled. In the following example, a condition is set on a property group section that only enables profiling when the app is built with `/p:ProfilingEnabled=true` (.NET CLI) or `<ProfilingEnabled>true</ProfilingEnabled>` in a Visual Studio publish profile.
+Enabling profilers has negative size and performance impact, so don't publish an app for production with profilers enabled. In the following example, a condition is set on a property group section that only enables profiling when the app is built with `/p:BlazorSampleProfilingEnabled=true` (.NET CLI) or `<BlazorSampleProfilingEnabled>true</BlazorSampleProfilingEnabled>` in a Visual Studio publish profile, where "`BlazorSampleProfilingEnabled`" is a custom symbol name that you choose and doesn't conflict with other symbol names.
 
 In the app's project file (`.csproj`):
 
 ```xml
-<PropertyGroup Condition="'$(ProfilingEnabled)' == 'true'">
+<PropertyGroup Condition="'$(BlazorSampleProfilingEnabled)' == 'true'">
   <WasmProfilers>browser;</WasmProfilers>
-  <RunAOTCompilation>true</RunAOTCompilation>
-  <RunAOTCompilationAfterBuild>true</RunAOTCompilationAfterBuild>
   <WasmNativeStrip>false</WasmNativeStrip>
   <WasmNativeDebugSymbols>true</WasmNativeDebugSymbols>
   <WasmBuildNative>true</WasmBuildNative>
 </PropertyGroup>
 ```
 
+Alternatively, enable features when the app is built with the .NET CLI. The following options passed to the `dotnet build` command mirror the preceding MS Build property configuration:
+
+```dotnetcli
+/p:WasmProfilers=browser /p:WasmNativeStrip=false /p:WasmNativeDebugSymbols=true /p:WasmBuildNative=true
+```
+
 Setting WebAssembly profilers with `<WasmProfilers>browser;</WasmProfilers>` doesn't require AOT (`<RunAOTCompilation>`/`<RunAOTCompilationAfterBuild>` set to `false` or removed from the preceding properity group).
 
 The browser developer tools profiler can be used with AOT (`<RunAOTCompilation>`/`<RunAOTCompilationAfterBuild>` set to `true`) and without WebAssembly profilers (`<WasmProfilers>browser;</WasmProfilers>` removed from the preceding property group).

aspnetcore/blazor/performance/event-pipe-profiling.md

@@ -1,22 +1,22 @@
 ---
-title: ASP.NET Core Blazor WebAssembly Event Pipe performance profiling and diagnostic counters
+title: ASP.NET Core Blazor WebAssembly Event Pipe diagnostic profiling
 author: guardrex
-description: Learn about Event Pipe performance profiling and diagnostic counters in ASP.NET Core Blazor WebAssembly apps.
+description: Learn about Event Pipe diagnostic profiling, counters, and how to get a Garbage Collector heap dump in ASP.NET Core Blazor WebAssembly apps.
 monikerRange: '>= aspnetcore-10.0'
 ms.author: riande
 ms.custom: mvc
-ms.date: 04/29/2025
-uid: blazor/performance/event-pipe-profiling
+ms.date: 04/30/2025
+uid: blazor/performance/event-pipe
 ---
-# ASP.NET Core Blazor WebAssembly Event Pipe performance profiling and diagnostic counters
+# ASP.NET Core Blazor WebAssembly Event Pipe diagnostic profiling
 
 <!-- UPDATE 10.0 - Activate ...
 
 [!INCLUDE[](~/includes/not-latest-version.md)]
 
 -->
 
-This article describes Event Pipe performance profiling tools and diagnostic counters for Blazor WebAssembly apps.
+This article describes Event Pipe diagnostic profiling tools, counters, and how to get a Garbage Collector heap dump in Blazor WebAssembly apps.
 
 ## Prerequisite
 
@@ -37,7 +37,7 @@ dotnet workload install wasm-tools
   * Upload the file via HTTP.
   * Parse and validate that the trace contains the expected method calls.
 
-Built-in performance counters are available to track:
+Built-in diagnostic counters are available to track:
 
 * [Ahead-of-time (AOT) compilation](xref:blazor/tooling/webassembly#ahead-of-time-aot-compilation)
 * Code interpolation
@@ -74,38 +74,44 @@ For more information, see the [.NET Core diagnostics documentation](/dotnet/core
 The following example:
 
 * Collects a GC (Garbage Collector) dump of the live .NET process.
-* Collects performance counters for 60 seconds.
+* Collects diagnostic counters for 60 seconds.
 * Collects CPU counters for 60 seconds.
 
 The MSBuild properties in the following table enable profiler integration.
 
 Property | Default | Set value to&hellip; | Description
 --- | :---: | :---: | ---
 `<WasmPerfTracing>` | `false` | `true` | Controls diagnostic server tracing.
-`<WasmPerfInstrumentation>` | `false` | `true` | Controls CPU sampling instrumentation for diagnostic server. Not necessary for memory dump or counters. **Makes the app execute slower. Only set this to `true` for performance profiling.
+`<WasmPerfInstrumentation>` | `false` | `true` | Controls CPU sampling instrumentation for diagnostic server. Not necessary for memory dump or counters. **Makes the app execute slower. Only set this to `true` for performance profiling.**
 `<MetricsSupport>` | `false` | `true` | Controls `System.Diagnostics.Metrics` support. For more information, see the [`System.Diagnostics.Metrics` namespace](/dotnet/api/system.diagnostics.metrics).
 `<EventSourceSupport>` | `false`| `true` | Controls `EventPipe` support. For more information, see [Diagnostics and instrumentation: Observability and telemetry](/dotnet/core/deploying/native-aot/diagnostics#observability-and-telemetry).
 
-Enabling profilers has negative size and performance impact, so don't publish an app for production with profilers enabled. In the following example, a condition is set on a property group section that only enables profiling when the app is built with `/p:ProfilingEnabled=true` (.NET CLI) or `<ProfilingEnabled>true</ProfilingEnabled>` in a Visual Studio publish profile.
+Enabling profilers has negative size and performance impact, so don't publish an app for production with profilers enabled. In the following example, a condition is set on a property group section that only enables profiling when the app is built with `/p:BlazorSampleProfilingEnabled=true` (.NET CLI) or `<BlazorSampleProfilingEnabled>true</BlazorSampleProfilingEnabled>` in a Visual Studio publish profile, where "`BlazorSampleProfilingEnabled`" is a custom symbol name that you choose and doesn't conflict with other symbol names.
 
 In the app's project file (`.csproj`):
 
 ```xml
-<PropertyGroup Condition="'$(ProfilingEnabled)' == 'true'">
+<PropertyGroup Condition="'$(BlazorSampleProfilingEnabled)' == 'true'">
   <WasmPerfTracing>true</WasmPerfTracing>
   <WasmPerfInstrumentation>true</WasmPerfInstrumentation>
   <MetricsSupport>true</MetricsSupport>
   <EventSourceSupport>true</EventSourceSupport>
 </PropertyGroup>
 ```
 
+Alternatively, enable features when the app is built with the .NET CLI. The following options passed to the `dotnet build` command mirror the preceding MS Build property configuration:
+
+```dotnetcli
+/p:WasmPerfTracing=true /p:WasmPerfInstrumentation=true /p:MetricsSupport=true /p:EventSourceSupport=true
+```
+
 The [`Timing-Allow-Origin` HTTP header](https://developer.mozilla.org/docs/Web/HTTP/Reference/Headers/Timing-Allow-Origin) allows for more precise time measurements.
 
 Browser developer tools console calls in the following example that trigger profiling:
 
 * `collectGcDump`: Collect a GC (Garbage Collector) dump.
-* `collectPerfCounters(durationSeconds)`: Collect general performance counters.
-* `collectCpuSamples(durationSeconds)`: Collect CPU performance counters.
+* `collectPerfCounters(durationSeconds)`: Collect general diagnostic counters.
+* `collectCpuSamples(durationSeconds)`: Collect CPU diagnostic counters.
 
 ```javascript
 globalThis.getDotnetRuntime(0).collectGcDump();

aspnetcore/performance/diagnostic-tools.md

@@ -13,7 +13,7 @@ By [Mike Rousos](https://github.com/mjrousos)
 
 This article lists tools for diagnosing performance issues in ASP.NET Core.
 
-For information on Blazor WebAssembly performance diagnostic tools and counters, see <xref:blazor/performance/developer-tools-profiling> and <xref:blazor/performance/event-pipe-profiling>.
+For information on Blazor WebAssembly performance diagnostic tools and counters, see <xref:blazor/performance/browser-developer-tools> and <xref:blazor/performance/event-pipe>.
 
 ## Visual Studio Diagnostic Tools
 

aspnetcore/release-notes/aspnetcore-10/includes/blazor.md

@@ -350,7 +350,7 @@ For more information, see the following sections of the *Call JavaScript functio
 
 New performance profiling and diagnostic counters are available for Blazor WebAssembly apps. For more information, see the following articles:
 
-* <xref:blazor/performance/developer-tools-profiling>
-* <xref:blazor/performance/event-pipe-profiling>
+* <xref:blazor/performance/browser-developer-tools>
+* <xref:blazor/performance/event-pipe>
 
 -->

aspnetcore/toc.yml

@@ -660,10 +660,10 @@ items:
                 uid: blazor/performance/app-download-size
               - name: JavaScript interop
                 uid: blazor/performance/js-interop
-              - name: WebAssembly developer tools profiling
-                uid: blazor/performance/developer-tools-profiling
-              - name: WebAssembly Event Pipe profiling
-                uid: blazor/performance/event-pipe-profiling
+              - name: WebAssembly browser developer tools diagnostics
+                uid: blazor/performance/browser-developer-tools
+              - name: WebAssembly Event Pipe diagnostics
+                uid: blazor/performance/event-pipe
           - name: Test components
             uid: blazor/test
           - name: Progressive Web Applications