Blazor Performance UE and pivot updates (#23135)

dotnet · Sep 2, 2021 · 9ed5d03 · 9ed5d03
1 parent 1203e32
commit 9ed5d03
Show file tree

Hide file tree

Showing 11 changed files with 2,030 additions and 1,982 deletions.
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -1027,7 +1027,7 @@
         },
         {
             "source_path": "aspnetcore/performance/blazor/webassembly-best-practices.md",
-            "redirect_url": "/aspnet/core/blazor/webassembly-performance-best-practices",
+            "redirect_url": "/aspnet/core/blazor/performance",
             "redirect_document_id": false
         },
         {
@@ -1153,6 +1153,11 @@
             "source_path": "aspnetcore/blazor/layouts.md",
             "redirect_url": "/aspnet/core/blazor/components/layouts",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/blazor/webassembly-performance-best-practices.md",
+            "redirect_url": "/aspnet/core/blazor/performance",
+            "redirect_document_id": false
         }
     ]
 }
diff --git a/aspnetcore/blazor/components/index.md b/aspnetcore/blazor/components/index.md
@@ -510,7 +510,7 @@ Alternatively, use a [`foreach`](/dotnet/csharp/language-reference/keywords/fore
 For information on how a <xref:Microsoft.AspNetCore.Components.RenderFragment> can be used as a template for component UI, see the following articles:
 
 * <xref:blazor/components/templated-components>
-* <xref:blazor/webassembly-performance-best-practices#define-reusable-renderfragments-in-code>
+* <xref:blazor/performance#define-reusable-renderfragments-in-code>
 
 ## Attribute splatting and arbitrary parameters
 
@@ -1501,7 +1501,7 @@ Alternatively, use a [`foreach`](/dotnet/csharp/language-reference/keywords/fore
 For information on how a <xref:Microsoft.AspNetCore.Components.RenderFragment> can be used as a template for component UI, see the following articles:
 
 * <xref:blazor/components/templated-components>
-* <xref:blazor/webassembly-performance-best-practices#define-reusable-renderfragments-in-code>
+* <xref:blazor/performance#define-reusable-renderfragments-in-code>
 
 ## Attribute splatting and arbitrary parameters
 
@@ -2440,7 +2440,7 @@ Alternatively, use a [`foreach`](/dotnet/csharp/language-reference/keywords/fore
 For information on how a <xref:Microsoft.AspNetCore.Components.RenderFragment> can be used as a template for component UI, see the following articles:
 
 * <xref:blazor/components/templated-components>
-* <xref:blazor/webassembly-performance-best-practices#define-reusable-renderfragments-in-code>
+* <xref:blazor/performance#define-reusable-renderfragments-in-code>
 
 ## Attribute splatting and arbitrary parameters
 

diff --git a/aspnetcore/blazor/components/rendering.md b/aspnetcore/blazor/components/rendering.md
@@ -33,7 +33,7 @@ Components inherited from <xref:Microsoft.AspNetCore.Components.ComponentBase> s
 
 In most cases, <xref:Microsoft.AspNetCore.Components.ComponentBase> conventions result in the correct subset of component rerenders after an event occurs. Developers aren't usually required to provide manual logic to tell the framework which components to rerender and when to rerender them. The overall effect of the framework's conventions is that the component receiving an event rerenders itself, which recursively triggers rerendering of descendant components whose parameter values may have changed.
 
-For more information on the performance implications of the framework's conventions and how to optimize an app's component hierarchy for rendering, see <xref:blazor/webassembly-performance-best-practices#optimize-rendering-speed>.
+For more information on the performance implications of the framework's conventions and how to optimize an app's component hierarchy for rendering, see <xref:blazor/performance#optimize-rendering-speed>.
 
 ## Suppress UI refreshing (`ShouldRender`)
 
@@ -45,7 +45,7 @@ Even if <xref:Microsoft.AspNetCore.Components.ComponentBase.ShouldRender%2A> is
 
 [!code-razor[](~/blazor/samples/6.0/BlazorSample_WebAssembly/Pages/rendering/ControlRender.razor)]
 
-For more information on performance best practices pertaining to <xref:Microsoft.AspNetCore.Components.ComponentBase.ShouldRender%2A>, see <xref:blazor/webassembly-performance-best-practices#avoid-unnecessary-rendering-of-component-subtrees>.
+For more information on performance best practices pertaining to <xref:Microsoft.AspNetCore.Components.ComponentBase.ShouldRender%2A>, see <xref:blazor/performance#avoid-unnecessary-rendering-of-component-subtrees>.
 
 ## When to call `StateHasChanged`
 
@@ -128,7 +128,7 @@ Components inherited from <xref:Microsoft.AspNetCore.Components.ComponentBase> s
 
 In most cases, <xref:Microsoft.AspNetCore.Components.ComponentBase> conventions result in the correct subset of component rerenders after an event occurs. Developers aren't usually required to provide manual logic to tell the framework which components to rerender and when to rerender them. The overall effect of the framework's conventions is that the component receiving an event rerenders itself, which recursively triggers rerendering of descendant components whose parameter values may have changed.
 
-For more information on the performance implications of the framework's conventions and how to optimize an app's component hierarchy for rendering, see <xref:blazor/webassembly-performance-best-practices#optimize-rendering-speed>.
+For more information on the performance implications of the framework's conventions and how to optimize an app's component hierarchy for rendering, see <xref:blazor/performance#optimize-rendering-speed>.
 
 ## Suppress UI refreshing (`ShouldRender`)
 
@@ -140,7 +140,7 @@ Even if <xref:Microsoft.AspNetCore.Components.ComponentBase.ShouldRender%2A> is
 
 [!code-razor[](~/blazor/samples/5.0/BlazorSample_WebAssembly/Pages/rendering/ControlRender.razor)]
 
-For more information on performance best practices pertaining to <xref:Microsoft.AspNetCore.Components.ComponentBase.ShouldRender%2A>, see <xref:blazor/webassembly-performance-best-practices#avoid-unnecessary-rendering-of-component-subtrees>.
+For more information on performance best practices pertaining to <xref:Microsoft.AspNetCore.Components.ComponentBase.ShouldRender%2A>, see <xref:blazor/performance#avoid-unnecessary-rendering-of-component-subtrees>.
 
 ## When to call `StateHasChanged`
 
@@ -223,7 +223,7 @@ Components inherited from <xref:Microsoft.AspNetCore.Components.ComponentBase> s
 
 In most cases, <xref:Microsoft.AspNetCore.Components.ComponentBase> conventions result in the correct subset of component rerenders after an event occurs. Developers aren't usually required to provide manual logic to tell the framework which components to rerender and when to rerender them. The overall effect of the framework's conventions is that the component receiving an event rerenders itself, which recursively triggers rerendering of descendant components whose parameter values may have changed.
 
-For more information on the performance implications of the framework's conventions and how to optimize an app's component hierarchy for rendering, see <xref:blazor/webassembly-performance-best-practices#optimize-rendering-speed>.
+For more information on the performance implications of the framework's conventions and how to optimize an app's component hierarchy for rendering, see <xref:blazor/performance#optimize-rendering-speed>.
 
 ## Suppress UI refreshing (`ShouldRender`)
 
@@ -235,7 +235,7 @@ Even if <xref:Microsoft.AspNetCore.Components.ComponentBase.ShouldRender%2A> is
 
 [!code-razor[](~/blazor/samples/3.1/BlazorSample_WebAssembly/Pages/rendering/ControlRender.razor)]
 
-For more information on performance best practices pertaining to <xref:Microsoft.AspNetCore.Components.ComponentBase.ShouldRender%2A>, see <xref:blazor/webassembly-performance-best-practices#avoid-unnecessary-rendering-of-component-subtrees>.
+For more information on performance best practices pertaining to <xref:Microsoft.AspNetCore.Components.ComponentBase.ShouldRender%2A>, see <xref:blazor/performance#avoid-unnecessary-rendering-of-component-subtrees>.
 
 ## When to call `StateHasChanged`
 

diff --git a/aspnetcore/blazor/components/templated-components.md b/aspnetcore/blazor/components/templated-components.md
@@ -132,7 +132,7 @@ For more information, see the following articles:
 
 ## Additional resources
 
-* <xref:blazor/webassembly-performance-best-practices#define-reusable-renderfragments-in-code>
+* <xref:blazor/performance#define-reusable-renderfragments-in-code>
 
 ::: moniker-end
 
@@ -183,7 +183,7 @@ Inferred generic types are supported in ASP.NET Core 6.0 or later. For more info
 
 ## Additional resources
 
-* <xref:blazor/webassembly-performance-best-practices#define-reusable-renderfragments-in-code>
+* <xref:blazor/performance#define-reusable-renderfragments-in-code>
 
 ::: moniker-end
 
@@ -234,6 +234,6 @@ Inferred generic types are supported in ASP.NET Core 6.0 or later. For more info
 
 ## Additional resources
 
-* <xref:blazor/webassembly-performance-best-practices#define-reusable-renderfragments-in-code>
+* <xref:blazor/performance#define-reusable-renderfragments-in-code>
 
 ::: moniker-end
diff --git a/aspnetcore/blazor/host-and-deploy/configure-linker.md b/aspnetcore/blazor/host-and-deploy/configure-linker.md
@@ -118,4 +118,4 @@ For more information, see [I18N: Pnetlib Internationalization Framework Library
 
 ## Additional resources
 
-* <xref:blazor/webassembly-performance-best-practices#intermediate-language-il-linking>
+* <xref:blazor/performance#intermediate-language-il-linking>
diff --git a/aspnetcore/blazor/host-and-deploy/configure-trimmer.md b/aspnetcore/blazor/host-and-deploy/configure-trimmer.md
@@ -30,7 +30,7 @@ To configure the Trimmer, see the [Trimming options](/dotnet/core/deploying/trim
 ## Additional resources
 
 * [Trim self-contained deployments and executables](/dotnet/core/deploying/trim-self-contained)
-* <xref:blazor/webassembly-performance-best-practices#intermediate-language-il-trimming>
+* <xref:blazor/performance#intermediate-language-il-trimming>
 
 ::: moniker-end
 
@@ -53,6 +53,6 @@ To configure the Trimmer, see the [Trimming options](/dotnet/core/deploying/trim
 ## Additional resources
 
 * [Trim self-contained deployments and executables](/dotnet/core/deploying/trim-self-contained)
-* <xref:blazor/webassembly-performance-best-practices#intermediate-language-il-trimming>
+* <xref:blazor/performance#intermediate-language-il-trimming>
 
 ::: moniker-end