Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions aspnetcore/blazor/components/js-spa-frameworks.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ description: Learn how to create and use Razor components in JavaScript apps and
monikerRange: '>= aspnetcore-6.0'
ms.author: wpickett
ms.custom: mvc
ms.date: 11/12/2024
ms.date: 10/26/2025
uid: blazor/components/js-spa-frameworks
---
# Use Razor components in JavaScript apps and SPA frameworks
Expand Down Expand Up @@ -241,13 +241,13 @@ For an advanced example with additional features, see the example in the `BasicT

:::moniker range=">= aspnetcore-7.0"

Use Blazor custom elements to dynamically render Razor components from other SPA frameworks, such as Angular or React.
Use Blazor custom elements to dynamically render Razor components from different JavaScript technologies, such as [Angular](https://angular.dev/), [React](https://react.dev/), and [Vue](https://vuejs.org/).

Blazor custom elements:

* Use standard HTML interfaces to implement custom HTML elements.
* Eliminate the need to manually manage the state and lifecycle of root Razor components using JavaScript APIs.
* Are useful for gradually introducing Razor components into existing projects written in other SPA frameworks.
* Are useful for gradually introducing Razor components into existing projects written in other technologies.

Custom elements don't support [child content](xref:blazor/components/index#child-content-render-fragments) or [templated components](xref:blazor/components/templated-components).

Expand Down Expand Up @@ -471,7 +471,7 @@ Use the custom element with any web framework. For example, the preceding counte

## Generate Angular and React components

Generate framework-specific JavaScript (JS) components from Razor components for web frameworks, such as Angular or React. This capability isn't included with .NET, but is enabled by the support for rendering Razor components from JS. The [JS component generation sample on GitHub](https://github.com/aspnet/samples/tree/main/samples/aspnetcore/blazor/JSComponentGeneration) demonstrates how to generate Angular and React components from Razor components. See the GitHub sample app's `README.md` file for additional information.
Generate JavaScript (JS) components from Razor components for JavaScript technologies, such as Angular or React. This capability isn't included with .NET, but is enabled by the support for rendering Razor components from JS. The [JS component generation sample on GitHub](https://github.com/aspnet/samples/tree/main/samples/aspnetcore/blazor/JSComponentGeneration) demonstrates how to generate Angular and React components from Razor components. See the GitHub sample app's `README.md` file for additional information.

> [!WARNING]
> The Angular and React component features are currently **experimental, unsupported, and subject to change or be removed at any time**. We welcome your feedback on how well this particular approach meets your requirements.
2 changes: 1 addition & 1 deletion aspnetcore/includes/spa-templates-recommend-vs.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ ms.author: tdykstra
ms.date: 10/10/2023
ms.topic: include
---
Visual Studio provides project templates for creating single-page apps (SPAs) based on JavaScript frameworks such as [Angular](https://angular.dev/), [React](https://react.dev/), and [Vue](https://vuejs.org/) that have an ASP.NET Core backend. These templates:
Visual Studio provides project templates for creating single-page apps (SPAs) based on JavaScript technologies, such as [Angular](https://angular.dev/), [React](https://react.dev/), and [Vue](https://vuejs.org/) that have an ASP.NET Core backend. These templates:

* Create a Visual Studio solution with a frontend project and a backend project.
* Use the Visual Studio project type for JavaScript and TypeScript (*.esproj*) for the frontend.
Expand Down
4 changes: 2 additions & 2 deletions aspnetcore/release-notes/aspnetcore-8.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ author: tdykstra
description: Learn about the new features in ASP.NET Core in .NET 8.
ms.author: tdykstra
ms.custom: mvc
ms.date: 05/02/2024
ms.date: 10/26/2025
uid: aspnetcore-8
---
# What's new in ASP.NET Core in .NET 8
Expand Down Expand Up @@ -869,7 +869,7 @@ The following sections describe miscellaneous new features in ASP.NET Core in .N

### Visual Studio project templates for SPA apps with ASP.NET Core backend

Visual Studio project templates are now the recommended way to create single-page apps (SPAs) that have an ASP.NET Core backend. Templates are provided that create apps based on the JavaScript frameworks [Angular](https://angular.dev/), [React](https://react.dev/), and [Vue](https://vuejs.org/). These templates:
Visual Studio project templates are now the recommended way to create single-page apps (SPAs) that have an ASP.NET Core backend. Templates are provided that create apps based on the JavaScript technologies, such as [Angular](https://angular.dev/), [React](https://react.dev/), and [Vue](https://vuejs.org/). These templates:

* Create a Visual Studio solution with a frontend project and a backend project.
* Use the Visual Studio project type for JavaScript and TypeScript (*.esproj*) for the frontend.
Expand Down
10 changes: 5 additions & 5 deletions aspnetcore/tutorials/choose-web-ui.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: Choose an ASP.NET Core UI
author: wadepickett
description: Learn when to use which ASP.NET Core web UI technologies. Understand the server, client and hybrid options.
ms.author: wpickett
ms.date: 12/04/2023
ms.date: 10/26/2025
uid: tutorials/choose-web-ui
---

Expand Down Expand Up @@ -59,15 +59,15 @@ ASP.NET Core MVC benefits:

To get started with ASP.NET Core MVC, see <xref:tutorials/first-mvc-app/start-mvc>. For an overview of ASP.NET Core MVC's architecture and benefits, see <xref:mvc/overview>.

## ASP.NET Core Single Page Applications (SPA) with frontend JavaScript frameworks
## ASP.NET Core Single Page Applications (SPA) with frontend JavaScript technologies

Build client-side logic for ASP.NET Core apps using popular JavaScript frameworks, like [Angular](https://angular.dev/), [React](https://react.dev/), and [Vue](https://vuejs.org/). ASP.NET Core provides project templates for Angular, React, and Vue, and it can be used with other JavaScript frameworks as well.
Build client-side logic for ASP.NET Core apps using popular JavaScript technologies, such as [Angular](https://angular.dev/), [React](https://react.dev/), and [Vue](https://vuejs.org/). ASP.NET Core provides project templates for Angular, React, and Vue, and it can be used with other JavaScript frameworks as well.

Benefits of ASP.NET Core SPA with JavaScript Frameworks, in addition to the client rendering benefits previously listed:
Benefits of ASP.NET Core SPA with JavaScript technologies, in addition to the client rendering benefits previously listed:

* The JavaScript runtime environment is already provided with the browser.
* Large community and mature ecosystem.
* Build client-side logic for ASP.NET Core apps using popular JS frameworks, like Angular, React, and Vue.
* Build client-side logic for ASP.NET Core apps using popular JavaScript technologies, such as Angular, React, and Vue.

Downsides:

Expand Down
12 changes: 6 additions & 6 deletions aspnetcore/tutorials/choose-web-ui/includes/choose-web-ui3-7.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,21 +45,21 @@ ASP.NET Core MVC benefits:
* Clear [separation of concerns](/dotnet/standard/modern-web-apps-azure-architecture/architectural-principles#separation-of-concerns) for maximum flexibility.
* The Model-View-Controller separation of responsibilities ensures that the business model can evolve without being tightly coupled to low-level implementation details.

To get started with ASP.NET Core MVC, see <xref:tutorials/first-mvc-app/start-mvc>. For an overview of ASP.NET Core MVC's architecture and benefits, see <xref:mvc/overview>.
To get started with ASP.NET Core MVC, see <xref:tutorials/first-mvc-app/start-mvc>. For an overview of ASP.NET Core MVC's architecture and benefits, see <xref:mvc/overview>.

## ASP.NET Core Single Page Applications (SPA) with frontend JavaScript frameworks
## ASP.NET Core Single Page Applications (SPA) with frontend JavaScript technologies

Build client-side logic for ASP.NET Core apps using popular JavaScript frameworks, like [Angular](https://angular.dev/), [React](https://react.dev/), and [Vue](https://vuejs.org/). ASP.NET Core provides project templates for Angular, React, and Vue, and it can be used with other JavaScript frameworks as well.
Build client-side logic for ASP.NET Core apps using popular JavaScript technologies, such as [Angular](https://angular.dev/), [React](https://react.dev/), and [Vue](https://vuejs.org/). ASP.NET Core provides project templates for Angular, React, and Vue, and it can be used with other JavaScript frameworks as well.

Benefits of ASP.NET Core SPA with JavaScript Frameworks, in addition to the client rendering benefits previously listed:
Benefits of ASP.NET Core SPA with JavaScript technologies, in addition to the client rendering benefits previously listed:

* The JavaScript runtime environment is already provided with the browser.
* Large community and mature ecosystem.
* Build client-side logic for ASP.NET Core apps using popular JS frameworks, like Angular, React, and Vue.
* Build client-side logic for ASP.NET Core apps using popular JavaScript technologies, such as Angular, React, and Vue.

Downsides:

* More coding languages, frameworks, and tools required.
* More coding languages and tools are required.
* Difficult to share code so some logic may be duplicated.

To get started, see:
Expand Down