Blazor cross-links (#33577)

aspnetcore/fundamentals/app-state.md

@@ -15,6 +15,8 @@ By [Rick Anderson](https://twitter.com/RickAndMSFT), [Kirk Larkin](https://twitt
 
 HTTP is a stateless protocol. By default, HTTP requests are independent messages that don't retain user values. This article describes several approaches to preserve user data between requests.
 
+For Blazor state management guidance, which adds to or supersedes the guidance in this article, see <xref:blazor/state-management>.
+
 ## State management
 
 State can be stored using several approaches. Each approach is described later in this article.

aspnetcore/fundamentals/configuration/index.md

@@ -29,6 +29,8 @@ Application configuration in ASP.NET Core is performed using one or more [config
 
 This article provides information on configuration in ASP.NET Core. For information on using configuration in console apps, see [.NET Configuration](/dotnet/core/extensions/configuration).
 
+For Blazor configuration guidance, which adds to or supersedes the guidance in this node, see <xref:blazor/fundamentals/configuration>.
+
 ## Application and Host Configuration
 
 ASP.NET Core apps configure and launch a *host*. The host is responsible for app startup and lifetime management. The ASP.NET Core templates create a <xref:Microsoft.AspNetCore.Builder.WebApplicationBuilder> which contains the host. While some configuration can be done in both the host and the application configuration providers, generally, only configuration that is necessary for the host should be done in host configuration.

aspnetcore/fundamentals/dependency-injection.md

@@ -25,6 +25,8 @@ For more information on dependency injection of options, see <xref:fundamentals/
 
 This topic provides information on dependency injection in ASP.NET Core. The primary documentation on using dependency injection is contained in [Dependency injection in .NET](/dotnet/core/extensions/dependency-injection).
 
+For Blazor DI guidance, which adds to or supersedes the guidance in this article, see <xref:blazor/fundamentals/dependency-injection>.
+
 [View or download sample code](https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/fundamentals/dependency-injection/samples) ([how to download](xref:index#how-to-download-a-sample))
 
 ## Overview of dependency injection

aspnetcore/fundamentals/environments.md

@@ -18,6 +18,8 @@ By [Rick Anderson](https://twitter.com/RickAndMSFT) and [Kirk Larkin](https://tw
 
 ASP.NET Core configures app behavior based on the runtime environment using an environment variable.
 
+For Blazor environments guidance, which adds to or supersedes the guidance in this article, see <xref:blazor/fundamentals/environments>.
+
 ## Environments
 
 :::moniker-end

aspnetcore/fundamentals/error-handling.md

@@ -18,6 +18,8 @@ By [Tom Dykstra](https://github.com/tdykstra/)
 
 This article covers common approaches to handling errors in ASP.NET Core web apps. See also <xref:web-api/handle-errors> and <xref:fundamentals/minimal-apis/handle-errors>.
 
+For Blazor error handling guidance, which adds to or supersedes the guidance in this article, see <xref:blazor/fundamentals/handle-errors>.
+
 ## Developer exception page
 
 [!INCLUDE [](../includes/developer-exception-page.md)]

aspnetcore/fundamentals/index.md

@@ -16,6 +16,8 @@ uid: fundamentals/index
 
 This article provides an overview of the fundamentals for building ASP.NET Core apps, including dependency injection (DI), configuration, middleware, and more.
 
+For Blazor fundamentals guidance, which adds to or supersedes the guidance in this node, see <xref:blazor/fundamentals/index>.
+
 ## Program.cs
 
 ASP.NET Core apps created with the web templates contain the application startup code in the `Program.cs` file. The `Program.cs` file is where:

aspnetcore/fundamentals/localization.md

@@ -17,6 +17,8 @@ By [Rick Anderson](https://twitter.com/RickAndMSFT), [Damien Bowden](https://twi
 
 A multilingual website allows a website to reach a wider audience. ASP.NET Core provides services and middleware for localizing into different languages and cultures.
 
+For Blazor localization guidance, which adds to or supersedes the guidance in this article, see <xref:blazor/globalization-localization>.
+
 ## Terms
 
 * Globalization (G11N): The process of making an app support different languages and regions. The abbreviation comes from the first and last letters and the number of letters between them.

aspnetcore/fundamentals/logging/index.md

@@ -17,7 +17,9 @@ uid: fundamentals/logging/index
 
 By [Kirk Larkin](https://twitter.com/serpent5), [Juergen Gutsch](https://github.com/JuergenGutsch), and [Rick Anderson](https://twitter.com/RickAndMSFT)
 
-This article describes logging in .NET as it applies to ASP.NET Core apps. For detailed information on logging in .NET, see [Logging in .NET](/dotnet/core/extensions/logging). For more information on logging in Blazor apps, see <xref:blazor/fundamentals/logging>.
+This article describes logging in .NET as it applies to ASP.NET Core apps. For detailed information on logging in .NET, see [Logging in .NET](/dotnet/core/extensions/logging).
+
+For Blazor logging guidance, which adds to or supersedes the guidance in this node, see <xref:blazor/fundamentals/logging>.
 
 <a name="lp"></a>
 

aspnetcore/fundamentals/native-aot.md

@@ -23,6 +23,8 @@ By [Mitch Denny](https://github.com/mitchdenny)
 
 ASP.NET Core 8.0 introduces support for [.NET native ahead-of-time (AOT)](/dotnet/core/deploying/native-aot/).
 
+For Blazor WebAssembly Native AOT guidance, which adds to or supersedes the guidance in this article, see <xref:blazor/tooling/webassembly>.
+
 ## Why use Native AOT with ASP.NET Core
 
 Publishing and deploying a Native AOT app provides the following benefits:

aspnetcore/fundamentals/routing.md

@@ -33,6 +33,7 @@ This article covers low-level details of ASP.NET Core routing. For information o
 
 * For controllers, see <xref:mvc/controllers/routing>.
 * For Razor Pages conventions, see <xref:razor-pages/razor-pages-conventions>.
+* For Blazor routing guidance, which adds to or supersedes the guidance in this article, see <xref:blazor/fundamentals/routing>.
 
 ## Routing basics
 

aspnetcore/fundamentals/startup.md

@@ -18,6 +18,8 @@ By [Rick Anderson](https://twitter.com/RickAndMSFT)
 
 ASP.NET Core apps created with the web templates contain the application startup code in the `Program.cs` file.
 
+For Blazor startup guidance, which adds to or supersedes the guidance in this article, see <xref:blazor/fundamentals/startup>.
+
 The following app startup code supports:
 
 * [Razor Pages](xref:tutorials/razor-pages/razor-pages-start)

aspnetcore/fundamentals/static-files.md

@@ -18,6 +18,8 @@ By [Rick Anderson](https://twitter.com/RickAndMSFT)
 
 Static files, such as HTML, CSS, images, and JavaScript, are assets an ASP.NET Core app serves directly to clients by default.
 
+For Blazor static files guidance, which adds to or supersedes the guidance in this article, see <xref:blazor/fundamentals/static-files>.
+
 ## Serve static files
 
 Static files are stored within the project's [web root](xref:fundamentals/index#web-root) directory. The default directory is `{content root}/wwwroot`, but it can be changed with the <xref:Microsoft.AspNetCore.Hosting.HostingAbstractionsWebHostBuilderExtensions.UseWebRoot%2A> method. For more information, see [Content root](xref:fundamentals/index#content-root) and [Web root](xref:fundamentals/index#web-root).
@@ -333,6 +335,8 @@ The following code updates `IWebHostEnvironment.WebRootPath` to a non developmen
 * [View or download sample code](https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/fundamentals/static-files/samples) ([how to download](xref:index#how-to-download-a-sample))
 * [Middleware](xref:fundamentals/middleware/index)
 * [Introduction to ASP.NET Core](xref:index)
+* <xref:blazor/file-uploads>
+* <xref:blazor/file-downloads>
 
 :::moniker-end
 

aspnetcore/getting-started/index.md

@@ -14,6 +14,8 @@ uid: getting-started
 
 This tutorial shows how to create and run an ASP.NET Core web app using the .NET CLI.
 
+For Blazor tutorials, see <xref:blazor/tutorials/index>.
+
 You'll learn how to:
 
 > [!div class="checklist"]

aspnetcore/host-and-deploy/index.md

@@ -20,6 +20,8 @@ In general, to deploy an ASP.NET Core app to a hosting environment:
 * Set up a process manager that starts the app when requests arrive and restarts the app after it crashes or the server reboots.
 * For configuration of a reverse proxy, set up a reverse proxy to forward requests to the app.
 
+For Blazor host and deploy guidance, which adds to or supersedes the guidance in this node, see <xref:blazor/host-and-deploy/index>.
+
 ## Publish to a folder
 
 The [dotnet publish](/dotnet/core/tools/dotnet-publish) command compiles app code and copies the files required to run the app into a *publish* folder. When deploying from Visual Studio, the `dotnet publish` step occurs automatically before the files are copied to the deployment destination.

aspnetcore/performance/overview.md

@@ -11,6 +11,9 @@ uid: performance/overview
 
 The following articles provide information about how to optimize the performance of ASP.NET Core apps:
 
+:::moniker range=">= aspnetcore-8.0"
+
+* <xref:blazor/performance>
 * <xref:fundamentals/best-practices>
 * <xref:performance/caching/overview>
 * <xref:performance/rate-limit>
@@ -20,7 +23,22 @@ The following articles provide information about how to optimize the performance
 * <xref:performance/response-compression>
 * <xref:performance/diagnostic-tools>
 * <xref:test/loadtests>
-:::moniker range=">= aspnetcore-8.0"
 * <xref:performance/timeouts>
 * [Short-circuit middleware after routing](xref:fundamentals/routing#short-circuit-middleware-after-routing)
+
+:::moniker-end
+
+:::moniker range="< aspnetcore-8.0"
+
+* <xref:blazor/performance>
+* <xref:fundamentals/best-practices>
+* <xref:performance/caching/overview>
+* <xref:performance/rate-limit>
+* <xref:performance/memory>
+* <xref:host-and-deploy/scaling-aspnet-apps/scaling-aspnet-apps>
+* <xref:performance/ObjectPool>
+* <xref:performance/response-compression>
+* <xref:performance/diagnostic-tools>
+* <xref:test/loadtests>
+
 :::moniker-end

aspnetcore/security/authentication/accconfirm.md

@@ -19,7 +19,7 @@ This tutorial shows how to build an ASP.NET Core app with email confirmation and
 
 :::moniker range=">= aspnetcore-8.0"
 
-For Blazor guidance, see <xref:blazor/security/server/account-confirmation-and-password-recovery>.
+For Blazor guidance, which adds to or supersedes the guidance in this article, see <xref:blazor/security/server/account-confirmation-and-password-recovery>.
 
 :::moniker-end
 

aspnetcore/signalr/configuration.md

@@ -11,6 +11,10 @@ uid: signalr/configuration
 
 # ASP.NET Core SignalR configuration
 
+This article covers ASP.NET Core SignalR configuration.
+
+For Blazor SignalR guidance, which adds to or supersedes the guidance in this article, see <xref:blazor/fundamentals/signalr>.
+
 :::moniker range=">= aspnetcore-8.0"
 
 ## JSON/MessagePack serialization options

aspnetcore/signalr/introduction.md

@@ -60,4 +60,5 @@ Hubs call client-side code by sending messages that contain the name and paramet
 * [Supported Platforms](xref:signalr/supported-platforms)
 * [Hubs](xref:signalr/hubs)
 * [JavaScript client](xref:signalr/javascript-client)
-* [Browsers that don't support ECMAScript 6 (ES6)](xref:signalr/supported-platforms#es6)
+* [Browsers that don't support ECMAScript 6 (ES6)](xref:signalr/supported-platforms#es6)
+* <xref:blazor/fundamentals/signalr>

aspnetcore/test/debug-aspnetcore-source.md

@@ -51,3 +51,4 @@ If you have debugged an app before with the previous version of .NET, delete the
 * [Limitations of the 'Suppress JIT optimization' option](/visualstudio/debugger/jit-optimization-and-debugging#limitations-of-the-suppress-jit-optimization-option) To set `COMPlus_ReadyToRun` to `0`
 * <xref:test/hot-reload>
 * [Test Execution with Hot Reload](/visualstudio/test/test-execution-with-hot-reload)
+* <xref:blazor/debug>

aspnetcore/toc.yml

@@ -1182,6 +1182,8 @@ items:
             uid: web-api/http-repl/telemetry
       - name: Test Minimal API
         uid: fundamentals/minimal-apis/test-min-api
+      - name: Blazor tests
+        uid: blazor/test
       - name: Razor Pages unit tests
         uid: test/razor-pages-tests
       - name: MVC controllers unit tests