Revert integration guidance to Blazor Server script (#34138)

Author: guardrex

.openpublishing.redirection.json

@@ -1117,7 +1117,7 @@
         },
         {
             "source_path": "aspnetcore/blazor/integrate-components.md",
-            "redirect_url": "/aspnet/core/blazor/components/prerendering-and-integration",
+            "redirect_url": "/aspnet/core/blazor/components/integration",
             "redirect_document_id": false
         },
         {
@@ -1157,7 +1157,7 @@
         },
         {
             "source_path": "aspnetcore/blazor/components/integrate-components-into-razor-pages-and-mvc-apps.md",
-            "redirect_url": "/aspnet/core/blazor/components/prerendering-and-integration",
+            "redirect_url": "/aspnet/core/blazor/components/integration",
             "redirect_document_id": false
         },
         {
@@ -1317,6 +1317,11 @@
             "source_path": "aspnetcore/blazor/images.md",
             "redirect_url": "/aspnet/core/blazor/images-and-documents",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/blazor/components/prerendering-and-integration.md",
+            "redirect_url": "/aspnet/core/blazor/components/integration",
+            "redirect_document_id": false
         }
     ]
 }

aspnetcore/blazor/components/index.md

@@ -1843,8 +1843,6 @@ In the preceding code, the CSS selector, `#app`, indicates that the `App` compon
 
 MVC and Razor Pages apps can also use the [Component Tag Helper](xref:Microsoft.AspNetCore.Mvc.TagHelpers.ComponentTagHelper) to register statically-rendered Blazor WebAssembly root components:
 
-:::moniker range=">= aspnetcore-6.0"
-
 ```cshtml
 <component type="typeof(App)" render-mode="WebAssemblyPrerendered" />
 ```
@@ -1853,22 +1851,9 @@ Statically-rendered components can only be added to the app. They can't be remov
 
 For more information, see the following resources:
 
-:::moniker-end
-
-:::moniker range=">= aspnetcore-8.0"
-
 * <xref:mvc/views/tag-helpers/builtin-th/component-tag-helper>
 * <xref:blazor/components/integration>
 
-:::moniker-end
-
-:::moniker range=">= aspnetcore-6.0 < aspnetcore-8.0"
-
-* <xref:mvc/views/tag-helpers/builtin-th/component-tag-helper>
-* <xref:blazor/components/prerendering-and-integration>
-
-:::moniker-end
-
 <!--Reference links in article-->
 [1]: <xref:mvc/views/razor#code>
 [2]: <xref:mvc/views/razor#using>

aspnetcore/blazor/components/integration.md

@@ -385,18 +385,8 @@ The following rendered HTML markup is produced by the preceding nested layout. E
 
 ## Share a Razor Pages layout with integrated components
 
-:::moniker range=">= aspnetcore-8.0"
-
 When routable components are integrated into a Razor Pages app, the app's shared layout can be used with the components. For more information, see <xref:blazor/components/integration>.
 
-:::moniker-end
-
-:::moniker range="< aspnetcore-8.0"
-
-When routable components are integrated into a Razor Pages app, the app's shared layout can be used with the components. For more information, see <xref:blazor/components/prerendering-and-integration>.
-
-:::moniker-end
-
 :::moniker range=">= aspnetcore-8.0"
 
 ## Sections

aspnetcore/blazor/components/layouts.md

@@ -206,7 +206,7 @@ To prevent developer code in <xref:Microsoft.AspNetCore.Components.ComponentBase
 
 :::moniker range="< aspnetcore-8.0"
 
-To prevent developer code in <xref:Microsoft.AspNetCore.Components.ComponentBase.OnInitializedAsync%2A> from running twice when prerendering, see the [Stateful reconnection after prerendering](#stateful-reconnection-after-prerendering) section. Although the content in the section focuses on Blazor Server and stateful SignalR *reconnection*, the scenario for prerendering in hosted Blazor WebAssembly solutions (<xref:Microsoft.AspNetCore.Mvc.Rendering.RenderMode.WebAssemblyPrerendered>) involves similar conditions and approaches to prevent executing developer code twice. To preserve state during the execution of initialization code while prerendering, see <xref:blazor/components/prerendering-and-integration#persist-prerendered-state>.
+To prevent developer code in <xref:Microsoft.AspNetCore.Components.ComponentBase.OnInitializedAsync%2A> from running twice when prerendering, see the [Stateful reconnection after prerendering](#stateful-reconnection-after-prerendering) section. Although the content in the section focuses on Blazor Server and stateful SignalR *reconnection*, the scenario for prerendering in hosted Blazor WebAssembly solutions (<xref:Microsoft.AspNetCore.Mvc.Rendering.RenderMode.WebAssemblyPrerendered>) involves similar conditions and approaches to prevent executing developer code twice. To preserve state during the execution of initialization code while prerendering, see <xref:blazor/components/integration#persist-prerendered-state>.
 
 :::moniker-end
 
@@ -612,7 +612,7 @@ The content in this section focuses on Blazor Web Apps and stateful SignalR *rec
 
 :::moniker range="< aspnetcore-8.0"
 
-Although the content in this section focuses on Blazor Server and stateful SignalR *reconnection*, the scenario for prerendering in hosted Blazor WebAssembly solutions (<xref:Microsoft.AspNetCore.Mvc.Rendering.RenderMode.WebAssemblyPrerendered>) involves similar conditions and approaches to prevent executing developer code twice. To preserve state during the execution of initialization code while prerendering, see <xref:blazor/components/prerendering-and-integration#persist-prerendered-state>.
+Although the content in this section focuses on Blazor Server and stateful SignalR *reconnection*, the scenario for prerendering in hosted Blazor WebAssembly solutions (<xref:Microsoft.AspNetCore.Mvc.Rendering.RenderMode.WebAssemblyPrerendered>) involves similar conditions and approaches to prevent executing developer code twice. To preserve state during the execution of initialization code while prerendering, see <xref:blazor/components/integration#persist-prerendered-state>.
 
 :::moniker-end