From 3652e1cf1968df0df6b0fca3060436b6736768b3 Mon Sep 17 00:00:00 2001 From: guardrex <1622880+guardrex@users.noreply.github.com> Date: Wed, 12 Nov 2025 15:54:36 -0500 Subject: [PATCH] ".NET Aspire" branding to "Aspire" --- aspnetcore/blazor/hybrid/class-libraries.md | 2 +- .../security/blazor-web-app-with-entra.md | 22 ++++++++----------- .../security/blazor-web-app-with-oidc.md | 22 ++++++++----------- aspnetcore/docfx.json | 2 +- .../openapi/aspnetcore-openapi.md | 2 +- .../openapi/includes/aspnetcore-openapi9.md | 2 +- .../AspireApp1.ServiceDefaults/Extensions.cs | 2 +- .../includes/signalrActivities.md | 4 ++-- aspnetcore/signalr/diagnostics.md | 4 ++-- 9 files changed, 27 insertions(+), 35 deletions(-) diff --git a/aspnetcore/blazor/hybrid/class-libraries.md b/aspnetcore/blazor/hybrid/class-libraries.md index 1e3093245aa2..b82f5283c994 100644 --- a/aspnetcore/blazor/hybrid/class-libraries.md +++ b/aspnetcore/blazor/hybrid/class-libraries.md @@ -60,7 +60,7 @@ The sample app showcases the following technologies: * [ASP.NET Core](https://dotnet.microsoft.com/apps/aspnet) * [Blazor](https://dotnet.microsoft.com/apps/aspnet/web-apps/blazor) * [.NET MAUI](https://dotnet.microsoft.com/apps/maui) -* [.NET Aspire](/dotnet/aspire/get-started/aspire-overview) +* [Aspire](/dotnet/aspire/get-started/aspire-overview) * [Docker](https://docs.docker.com/get-started/docker-overview/) ## Share web UI Razor components, code, and static assets diff --git a/aspnetcore/blazor/security/blazor-web-app-with-entra.md b/aspnetcore/blazor/security/blazor-web-app-with-entra.md index fc8b7c251a17..92353eed044e 100644 --- a/aspnetcore/blazor/security/blazor-web-app-with-entra.md +++ b/aspnetcore/blazor/security/blazor-web-app-with-entra.md @@ -217,7 +217,7 @@ The following specification is covered: * The server project calls to add a server-side authentication state provider that uses to flow the authentication state to the client. The client calls to deserialize and use the authentication state passed by the server. The authentication state is fixed for the lifetime of the WebAssembly application. * The app uses [Microsoft Entra ID](https://www.microsoft.com/security/business/microsoft-entra), based on [Microsoft Identity Web](/entra/msal/dotnet/microsoft-identity-web/) packages. * Automatic non-interactive token refresh is managed by the framework. -* The [Backend for Frontend (BFF) pattern](/azure/architecture/patterns/backends-for-frontends) is adopted using [.NET Aspire](/dotnet/aspire/get-started/aspire-overview) for service discovery and [YARP](https://dotnet.github.io/yarp/) for proxying requests to a weather forecast endpoint on the backend app. +* The [Backend for Frontend (BFF) pattern](/azure/architecture/patterns/backends-for-frontends) is adopted using [Aspire](/dotnet/aspire/get-started/aspire-overview) for service discovery and [YARP](https://dotnet.github.io/yarp/) for proxying requests to a weather forecast endpoint on the backend app. * A backend web API uses JWT-bearer authentication to validate JWT tokens saved by the Blazor Web App in the sign-in cookie. * Aspire improves the experience of building .NET cloud-native apps. It provides a consistent, opinionated set of tools and patterns for building and running distributed apps. * YARP (Yet Another Reverse Proxy) is a library used to create a reverse proxy server. @@ -225,23 +225,19 @@ The following specification is covered: * When rendering the `Weather` component on the server to display weather data, the component uses the `ServerWeatherForecaster`. Microsoft Identity Web packages provide API to create a named downstream web service for making web API calls. is injected into the `ServerWeatherForecaster`, which is used to call to obtain weather data from an external web API (`MinimalApiJwt` project). * When the `Weather` component is rendered on the client, the component uses the `ClientWeatherForecaster` service implementation, which uses a preconfigured (in the client project's `Program` file) to make a web API call to the server project's Minimal API (`/weather-forecast`) for weather data. The Minimal API endpoint obtains an access token for the user by calling . Along with the correct scopes, a reverse proxy call is made to the external web API (`MinimalApiJwt` project) to obtain and return weather data to the client for rendering by the component. - - -For more information on .NET Aspire, see [General Availability of .NET Aspire: Simplifying .NET Cloud-Native Development (May, 2024)](https://devblogs.microsoft.com/dotnet/dotnet-aspire-general-availability/). - ## Prerequisites -[.NET Aspire](/dotnet/aspire/get-started/aspire-overview) requires [Visual Studio](https://visualstudio.microsoft.com/) version 17.10 or later. +[Aspire](/dotnet/aspire/get-started/aspire-overview) requires [Visual Studio](https://visualstudio.microsoft.com/) version 17.10 or later. -Also, see the *Prerequisites* section of [Quickstart: Build your first .NET Aspire app](/dotnet/aspire/get-started/build-your-first-aspire-app?tabs=visual-studio#prerequisites). +Also, see the *Prerequisites* section of [Quickstart: Build your first Aspire solution](/dotnet/aspire/get-started/build-your-first-aspire-app?tabs=visual-studio#prerequisites). ## Sample solution The sample solution consists of the following projects: -* .NET Aspire: +* Aspire: * `Aspire.AppHost`: Used to manage the high-level orchestration concerns of the app. - * `Aspire.ServiceDefaults`: Contains default .NET Aspire app configurations that can be extended and customized as needed. + * `Aspire.ServiceDefaults`: Contains default Aspire app configurations that can be extended and customized as needed. * `MinimalApiJwt`: Backend web API, containing an example [Minimal API](xref:fundamentals/minimal-apis) endpoint for weather data. * `BlazorWebAppEntra`: Server-side project of the Blazor Web App. * `BlazorWebAppEntra.Client`: Client-side project of the Blazor Web App. @@ -264,13 +260,13 @@ Create a client secret in the app's registration in the Entra or Azure portal (* Additional Entra configuration guidance for specific settings is provided later in this article. -## .NET Aspire projects +## Aspire projects -For more information on using .NET Aspire and details on the `.AppHost` and `.ServiceDefaults` projects of the sample app, see the [.NET Aspire documentation](/dotnet/aspire/). +For more information on using Aspire and details on the `.AppHost` and `.ServiceDefaults` projects of the sample app, see the [Aspire documentation](/dotnet/aspire/). -Confirm that you've met the prerequisites for .NET Aspire. For more information, see the *Prerequisites* section of [Quickstart: Build your first .NET Aspire app](/dotnet/aspire/get-started/build-your-first-aspire-app?tabs=visual-studio#prerequisites). +Confirm that you've met the prerequisites for Aspire. For more information, see the *Prerequisites* section of [Quickstart: Build your first Aspire solution](/dotnet/aspire/get-started/build-your-first-aspire-app?tabs=visual-studio#prerequisites). -The sample app only configures an insecure HTTP launch profile (`http`) for use during development testing. For more information, including an example of insecure and secure launch settings profiles, see [Allow unsecure transport in .NET Aspire (.NET Aspire documentation)](/dotnet/aspire/troubleshooting/allow-unsecure-transport). +The sample app only configures an insecure HTTP launch profile (`http`) for use during development testing. For more information, including an example of insecure and secure launch settings profiles, see [Allow unsecure transport in Aspire (Aspire documentation)](/dotnet/aspire/troubleshooting/allow-unsecure-transport). ## Server-side Blazor Web App project (`BlazorWebAppEntra`) diff --git a/aspnetcore/blazor/security/blazor-web-app-with-oidc.md b/aspnetcore/blazor/security/blazor-web-app-with-oidc.md index 470c84abf01b..880281e59a81 100644 --- a/aspnetcore/blazor/security/blazor-web-app-with-oidc.md +++ b/aspnetcore/blazor/security/blazor-web-app-with-oidc.md @@ -770,17 +770,17 @@ This version of the article covers implementing OIDC with the [Backend for Front ## Prerequisites -[.NET Aspire](/dotnet/aspire/get-started/aspire-overview) requires [Visual Studio](https://visualstudio.microsoft.com/) version 17.10 or later. +[Aspire](/dotnet/aspire/get-started/aspire-overview) requires [Visual Studio](https://visualstudio.microsoft.com/) version 17.10 or later. -Also, see the *Prerequisites* section of [Quickstart: Build your first .NET Aspire app](/dotnet/aspire/get-started/build-your-first-aspire-app?tabs=visual-studio#prerequisites). +Also, see the *Prerequisites* section of [Quickstart: Build your first Aspire solution](/dotnet/aspire/get-started/build-your-first-aspire-app?tabs=visual-studio#prerequisites). ## Sample solution The sample app consists of the following projects: -* .NET Aspire: +* Aspire: * `Aspire.AppHost`: Used to manage the high-level orchestration concerns of the app. - * `Aspire.ServiceDefaults`: Contains default .NET Aspire app configurations that can be extended and customized as needed. + * `Aspire.ServiceDefaults`: Contains default Aspire app configurations that can be extended and customized as needed. * `MinimalApiJwt`: Backend web API, containing an example [Minimal API](xref:fundamentals/minimal-apis) endpoint for weather data. * `BlazorWebAppOidc`: Server-side project of the Blazor Web App. The project uses [YARP](https://dotnet.github.io/yarp/) to proxy requests to a weather forecast endpoint in the backend web API project (`MinimalApiJwt`) with the `access_token` stored in the authentication cookie. * `BlazorWebAppOidc.Client`: Client-side project of the Blazor Web App. @@ -807,7 +807,7 @@ This app is a starting point for any OIDC authentication flow. OIDC is configure Automatic non-interactive token refresh with the help of a custom cookie refresher (`CookieOidcRefresher.cs`). -The [Backend for Frontend (BFF) pattern](/azure/architecture/patterns/backends-for-frontends) is adopted using [.NET Aspire](/dotnet/aspire/get-started/aspire-overview) for service discovery and [YARP](https://dotnet.github.io/yarp/) for proxying requests to a weather forecast endpoint on the backend app. +The [Backend for Frontend (BFF) pattern](/azure/architecture/patterns/backends-for-frontends) is adopted using [Aspire](/dotnet/aspire/get-started/aspire-overview) for service discovery and [YARP](https://dotnet.github.io/yarp/) for proxying requests to a weather forecast endpoint on the backend app. The backend web API (`MinimalApiJwt`) uses JWT-bearer authentication to validate JWT tokens saved by the Blazor Web App in the sign-in cookie. @@ -818,10 +818,6 @@ YARP (Yet Another Reverse Proxy) is a library used to create a reverse proxy ser * When rendering the `Weather` component on the server, the component uses the `ServerWeatherForecaster` class to proxy the request for weather data with the user's access token. determines if an is available for use by the `GetWeatherForecastAsync` method. For more information, see . * When the component is rendered on the client, the component uses the `ClientWeatherForecaster` service implementation, which uses a preconfigured (in the client project's `Program` file) to make a web API call to the server project. A Minimal API endpoint (`/weather-forecast`) defined in the server project's `Program` file transforms the request with the user's access token to obtain the weather data. - - -For more information on .NET Aspire, see [General Availability of .NET Aspire: Simplifying .NET Cloud-Native Development (May, 2024)](https://devblogs.microsoft.com/dotnet/dotnet-aspire-general-availability/). - For more information on (web) API calls using a service abstractions in Blazor Web Apps, see . ## Microsoft Entra ID app registrations @@ -860,13 +856,13 @@ dotnet user-secrets set "Authentication:Schemes:MicrosoftOidc:ClientSecret" "{SE If using Visual Studio, you can confirm the secret is set by right-clicking the server project in **Solution Explorer** and selecting **Manage User Secrets**. -## .NET Aspire projects +## Aspire projects -For more information on using .NET Aspire and details on the `.AppHost` and `.ServiceDefaults` projects of the sample app, see the [.NET Aspire documentation](/dotnet/aspire/). +For more information on using Aspire and details on the `.AppHost` and `.ServiceDefaults` projects of the sample app, see the [Aspire documentation](/dotnet/aspire/). -Confirm that you've met the prerequisites for .NET Aspire. For more information, see the *Prerequisites* section of [Quickstart: Build your first .NET Aspire app](/dotnet/aspire/get-started/build-your-first-aspire-app?tabs=visual-studio#prerequisites). +Confirm that you've met the prerequisites for Aspire. For more information, see the *Prerequisites* section of [Quickstart: Build your first Aspire solution](/dotnet/aspire/get-started/build-your-first-aspire-app?tabs=visual-studio#prerequisites). -The sample app only configures an insecure HTTP launch profile (`http`) for use during development testing. For more information, including an example of insecure and secure launch settings profiles, see [Allow unsecure transport in .NET Aspire (.NET Aspire documentation)](/dotnet/aspire/troubleshooting/allow-unsecure-transport). +The sample app only configures an insecure HTTP launch profile (`http`) for use during development testing. For more information, including an example of insecure and secure launch settings profiles, see [Allow unsecure transport in Aspire (Aspire documentation)](/dotnet/aspire/troubleshooting/allow-unsecure-transport). ## `MinimalApiJwt` project diff --git a/aspnetcore/docfx.json b/aspnetcore/docfx.json index d48ead00f5a4..255d04df7c41 100644 --- a/aspnetcore/docfx.json +++ b/aspnetcore/docfx.json @@ -89,7 +89,7 @@ "**/**.{md,yml}": "365-days" }, "no-loc": { - "**/**.md": [ "Blazor", "Blazor Hybrid", "Blazor Server", "Blazor WebAssembly", "Blazor Web App", "BREACH", "cookie", "Cookie", "CRIME", "EF Core", "Home" , "global.json", "Identity", "JS", "Kestrel", ".NET Aspire", ".NET MAUI", ".NET Multi-platform App UI", "Privacy", "QuickGrid", "Razor", "REST", "SignalR", "Web View" ] + "**/**.md": [ "Blazor", "Blazor Hybrid", "Blazor Server", "Blazor WebAssembly", "Blazor Web App", "BREACH", "cookie", "Cookie", "CRIME", "EF Core", "Home" , "global.json", "Identity", "JS", "Kestrel", "Aspire", ".NET MAUI", ".NET Multi-platform App UI", "Privacy", "QuickGrid", "Razor", "REST", "SignalR", "Web View" ] }, "recommendations": { "**/tutorials/**/**.md": "false" diff --git a/aspnetcore/fundamentals/openapi/aspnetcore-openapi.md b/aspnetcore/fundamentals/openapi/aspnetcore-openapi.md index 81932a990742..d0c58aaad1cd 100644 --- a/aspnetcore/fundamentals/openapi/aspnetcore-openapi.md +++ b/aspnetcore/fundamentals/openapi/aspnetcore-openapi.md @@ -301,7 +301,7 @@ In order to restrict invoking these code paths by the build-time generation pipe :::code language="csharp" source="~/fundamentals/openapi/samples/9.x/AspireApp1/AspireApp1.Web/Program.cs" highlight="5-8"::: -[`AddServiceDefaults`](https://source.dot.net/#TestingAppHost1.ServiceDefaults/Extensions.cs,0f0d863053754768,references) adds common .NET Aspire services such as service discovery, resilience, health checks, and OpenTelemetry. +[`AddServiceDefaults`](https://source.dot.net/#TestingAppHost1.ServiceDefaults/Extensions.cs,0f0d863053754768,references) adds common Aspire services such as service discovery, resilience, health checks, and OpenTelemetry. ## Trimming and Native AOT diff --git a/aspnetcore/fundamentals/openapi/includes/aspnetcore-openapi9.md b/aspnetcore/fundamentals/openapi/includes/aspnetcore-openapi9.md index 08ea7d28a184..c85061c33abe 100644 --- a/aspnetcore/fundamentals/openapi/includes/aspnetcore-openapi9.md +++ b/aspnetcore/fundamentals/openapi/includes/aspnetcore-openapi9.md @@ -235,7 +235,7 @@ In order to restrict these code paths from being invoked by the build-time gener :::code language="csharp" source="~/fundamentals/openapi/samples/9.x/AspireApp1/AspireApp1.Web/Program.cs" highlight="5-8"::: -[AddServiceDefaults](https://source.dot.net/#TestingAppHost1.ServiceDefaults/Extensions.cs,0f0d863053754768,references) adds common .NET Aspire services such as service discovery, resilience, health checks, and OpenTelemetry. +[AddServiceDefaults](https://source.dot.net/#TestingAppHost1.ServiceDefaults/Extensions.cs,0f0d863053754768,references) adds common Aspire services such as service discovery, resilience, health checks, and OpenTelemetry. ## Trimming and Native AOT diff --git a/aspnetcore/fundamentals/openapi/samples/9.x/AspireApp1/AspireApp1.ServiceDefaults/Extensions.cs b/aspnetcore/fundamentals/openapi/samples/9.x/AspireApp1/AspireApp1.ServiceDefaults/Extensions.cs index 13151bf46d90..b75192e87b3a 100644 --- a/aspnetcore/fundamentals/openapi/samples/9.x/AspireApp1/AspireApp1.ServiceDefaults/Extensions.cs +++ b/aspnetcore/fundamentals/openapi/samples/9.x/AspireApp1/AspireApp1.ServiceDefaults/Extensions.cs @@ -10,7 +10,7 @@ namespace Microsoft.Extensions.Hosting; -// Adds common .NET Aspire services: service discovery, resilience, health checks, and OpenTelemetry. +// Adds common Aspire services: service discovery, resilience, health checks, and OpenTelemetry. // This project should be referenced by each service project in your solution. // To learn more about using this project, see https://aka.ms/dotnet/aspire/service-defaults public static class Extensions diff --git a/aspnetcore/release-notes/aspnetcore-9/includes/signalrActivities.md b/aspnetcore/release-notes/aspnetcore-9/includes/signalrActivities.md index b9fe757842c7..bdfdf05e3a86 100644 --- a/aspnetcore/release-notes/aspnetcore-9/includes/signalrActivities.md +++ b/aspnetcore/release-notes/aspnetcore-9/includes/signalrActivities.md @@ -9,7 +9,7 @@ The SignalR ActivitySource named `Microsoft.AspNetCore.SignalR.Server` emits eve * Every method is its own activity, so anything that emits an activity during the hub method call is under the hub method activity. * Hub method activities don't have a parent. This means they are not bundled under the long-running SignalR connection. -The following example uses the [.NET Aspire dashboard](/dotnet/aspire/fundamentals/dashboard/overview?tabs=bash#using-the-dashboard-with-net-aspire-projects) and the [OpenTelemetry](https://www.nuget.org/packages/OpenTelemetry.Extensions.Hosting) packages: +The following example uses the [Aspire dashboard](/dotnet/aspire/fundamentals/dashboard/overview?tabs=bash#use-the-dashboard-with-aspire-projects) and the [OpenTelemetry](https://www.nuget.org/packages/OpenTelemetry.Extensions.Hosting) packages: ```xml @@ -32,6 +32,6 @@ The SignalR ActivitySource named `Microsoft.AspNetCore.SignalR.Client` emits eve * The .NET SignalR client has an `ActivitySource` named `Microsoft.AspNetCore.SignalR.Client`. Hub invocations now create a client span. Note that other SignalR clients, such as the JavaScript client, don't support tracing. This feature will be added to more clients in future releases. * Hub invocations on the client and server support [context propagation](https://opentelemetry.io/docs/concepts/context-propagation/). Propagating the trace context enables true distributed tracing. It's now possible to see invocations flow from the client to the server and back. -Here's how these new activities look in the [.NET Aspire dashboard](/dotnet/aspire/fundamentals/dashboard/overview?tabs=bash#standalone-mode): +Here's how these new activities look in the [Aspire dashboard](/dotnet/aspire/fundamentals/dashboard/overview?tabs=bash#standalone-mode): ![SignalR distributed tracing in Aspire dashboard](~/release-notes/aspnetcore-9/_static/signalr-distributed-tracing-aspire-dashboard.png) diff --git a/aspnetcore/signalr/diagnostics.md b/aspnetcore/signalr/diagnostics.md index fa5e4223101d..818fecf654ec 100644 --- a/aspnetcore/signalr/diagnostics.md +++ b/aspnetcore/signalr/diagnostics.md @@ -151,7 +151,7 @@ The SignalR ActivitySource named `Microsoft.AspNetCore.SignalR.Server` emits eve * Every method is its own activity, so anything that emits an activity during the hub method call is under the hub method activity. * Hub method activities don't have a parent. This means they aren't bundled under the long-running SignalR connection. -The following example uses the [.NET Aspire dashboard](/dotnet/aspire/fundamentals/dashboard/overview?tabs=bash#using-the-dashboard-with-net-aspire-projects) and the [OpenTelemetry](https://www.nuget.org/packages/OpenTelemetry.Extensions.Hosting) packages: +The following example uses the [Aspire dashboard](/dotnet/aspire/fundamentals/dashboard/overview?tabs=bash#use-the-dashboard-with-aspire-projects) and the [OpenTelemetry](https://www.nuget.org/packages/OpenTelemetry.Extensions.Hosting) packages: ```xml @@ -176,7 +176,7 @@ The SignalR `ActivitySource` named `Microsoft.AspNetCore.SignalR.Client` emits e * Hub invocations create a client span. Other SignalR clients, such as the JavaScript client, don't support tracing. This feature will be added to more clients in future releases. * Hub invocations on the client and server support [context propagation](https://opentelemetry.io/docs/concepts/context-propagation/). Propagating the trace context enables true distributed tracing. It's now possible to see invocations flow from the client to the server and back. -Here's how these new activities look in the [.NET Aspire dashboard](/dotnet/aspire/fundamentals/dashboard/overview?tabs=bash#standalone-mode): +Here's how these new activities look in the [Aspire dashboard](/dotnet/aspire/fundamentals/dashboard/overview?tabs=bash#standalone-mode): ![SignalR distributed tracing in Aspire dashboard](~/signalr/diagnostics/_static/9.x/signalr-distributed-tracing-aspire-dashboard.png)