Skip to content

Commit 092b283

Browse files
Merge pull request #33871 from timdeschryver/issue/32992
update Angular references to new website
2 parents 117fef4 + 7efd129 commit 092b283

File tree

10 files changed

+17
-17
lines changed

10 files changed

+17
-17
lines changed

aspnetcore/client-side/spa-services.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ By [Fiyaz Hasan](https://fiyazhasan.me/)
1919
2020
:::moniker-end
2121

22-
A Single Page Application (SPA) is a popular type of web application due to its inherent rich user experience. Integrating client-side SPA frameworks or libraries, such as [Angular](https://angular.io/) or [React](https://facebook.github.io/react/), with server-side frameworks such as ASP.NET Core can be difficult. JavaScript Services was developed to reduce friction in the integration process. It enables seamless operation between the different client and server technology stacks.
22+
A Single Page Application (SPA) is a popular type of web application due to its inherent rich user experience. Integrating client-side SPA frameworks or libraries, such as [Angular](https://angular.dev/) or [React](https://react.dev/), with server-side frameworks such as ASP.NET Core can be difficult. JavaScript Services was developed to reduce friction in the integration process. It enables seamless operation between the different client and server technology stacks.
2323

2424
## What is JavaScript Services
2525

@@ -305,4 +305,4 @@ dotnet publish -c Release
305305

306306
## Additional resources
307307

308-
* [Angular Docs](https://angular.io/docs)
308+
* [Angular Docs](https://angular.dev/docs)

aspnetcore/client-side/spa-services/sample/SpaServicesSampleApp/ClientApp/app/components/home/home.component.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ <h1>Hello, world!</h1>
22
<p>Welcome to your new single-page application, built with:</p>
33
<ul>
44
<li><a href='https://get.asp.net/'>ASP.NET Core</a> and <a href='https://msdn.microsoft.com/library/67ef8sbd.aspx'>C#</a> for cross-platform server-side code</li>
5-
<li><a href='https://angular.io/'>Angular</a> and <a href='http://www.typescriptlang.org/'>TypeScript</a> for client-side code</li>
5+
<li><a href='https://angular.dev/'>Angular</a> and <a href='http://www.typescriptlang.org/'>TypeScript</a> for client-side code</li>
66
<li><a href='https://webpack.github.io/'>Webpack</a> for building and bundling client-side resources</li>
77
<li><a href='http://getbootstrap.com/'>Bootstrap</a> for layout and styling</li>
88
</ul>

aspnetcore/client-side/spa/includes/angular3-7.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ The project template creates an ASP.NET Core app and an Angular app. The ASP.NET
3939

4040
## Add pages, images, styles, and modules
4141

42-
The `ClientApp` directory contains a standard Angular CLI app. See the official [Angular documentation](https://angular.io) for more information.
42+
The `ClientApp` directory contains a standard Angular CLI app. See the official [Angular documentation](https://angular.dev) for more information.
4343

4444
There are slight differences between the Angular app created by this template and the one created by Angular CLI itself (via `ng new`); however, the app's capabilities are unchanged. The app created by the template contains a [Bootstrap](https://getbootstrap.com/)-based layout and a basic routing example.
4545

@@ -51,7 +51,7 @@ In a command prompt, switch to the `ClientApp` subdirectory:
5151
cd ClientApp
5252
```
5353

54-
If you have the `ng` tool installed globally, you can run any of its commands. For example, you can run `ng lint`, `ng test`, or any of the other [Angular CLI commands](https://angular.io/cli). There's no need to run `ng serve` though, because your ASP.NET Core app deals with serving both server-side and client-side parts of your app. Internally, it uses `ng serve` in development.
54+
If you have the `ng` tool installed globally, you can run any of its commands. For example, you can run `ng lint`, `ng test`, or any of the other [Angular CLI commands](https://angular.dev/cli). There's no need to run `ng serve` though, because your ASP.NET Core app deals with serving both server-side and client-side parts of your app. Internally, it uses `ng serve` in development.
5555

5656
If you don't have the `ng` tool installed, run `npm run ng` instead. For example, you can run `npm run ng lint` or `npm run ng test`.
5757

@@ -144,7 +144,7 @@ The project template creates an ASP.NET Core app and an Angular app. The ASP.NET
144144

145145
## Add pages, images, styles, and modules
146146

147-
The `ClientApp` directory contains a standard Angular CLI app. See the official [Angular documentation](https://angular.io) for more information.
147+
The `ClientApp` directory contains a standard Angular CLI app. See the official [Angular documentation](https://angular.dev) for more information.
148148

149149
There are slight differences between the Angular app created by this template and the one created by Angular CLI itself (via `ng new`); however, the app's capabilities are unchanged. The app created by the template contains a [Bootstrap](https://getbootstrap.com/)-based layout and a basic routing example.
150150

@@ -156,7 +156,7 @@ In a command prompt, switch to the `ClientApp` subdirectory:
156156
cd ClientApp
157157
```
158158

159-
If you have the `ng` tool installed globally, you can run any of its commands. For example, you can run `ng lint`, `ng test`, or any of the other [Angular CLI commands](https://angular.io/cli). There's no need to run `ng serve` though, because your ASP.NET Core app deals with serving both server-side and client-side parts of your app. Internally, it uses `ng serve` in development.
159+
If you have the `ng` tool installed globally, you can run any of its commands. For example, you can run `ng lint`, `ng test`, or any of the other [Angular CLI commands](https://angular.dev/cli). There's no need to run `ng serve` though, because your ASP.NET Core app deals with serving both server-side and client-side parts of your app. Internally, it uses `ng serve` in development.
160160

161161
If you don't have the `ng` tool installed, run `npm run ng` instead. For example, you can run `npm run ng lint` or `npm run ng test`.
162162

aspnetcore/client-side/spa/includes/intro6-7.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33

44
## Architecture of Single Page Application templates
55

6-
The Single Page Application (SPA) templates for [Angular](https://angular.io/) and [React](https://reactjs.org/) offer the ability to develop Angular and React apps that are hosted inside a .NET backend server.
6+
The Single Page Application (SPA) templates for [Angular](https://angular.dev/) and [React](https://reactjs.org/) offer the ability to develop Angular and React apps that are hosted inside a .NET backend server.
77

88
At publish time, the files of the Angular and React app are copied to the `wwwroot` folder and are served via the [static files middleware](xref:fundamentals/static-files).
99

@@ -77,7 +77,7 @@ The template generated `ClientApp/package.json` file:
7777
* The `prestart` script invokes `ClientApp/aspnetcore-https.js`, which is responsible for ensuring the development server HTTPS certificate is available to the SPA proxy server.
7878
* The `start:windows` and `start:default`:
7979

80-
* Launch the Angular development server via [`ng serve`](https://angular.io/cli/serve).
80+
* Launch the Angular development server via [`ng serve`](https://angular.dev/cli/serve).
8181
* Provide the port, the options to use HTTPS, and the path to the certificate and the associated key. The provide port number matches the port number specified in the `.csproj` file.
8282

8383
The template generated `ClientApp/angular.json` file contains:

aspnetcore/includes/spa-templates-recommend-vs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ ms.author: tdykstra
44
ms.date: 10/10/2023
55
ms.topic: include
66
---
7-
Visual Studio provides project templates for creating single-page apps (SPAs) based on JavaScript frameworks such as [Angular](https://angular.io/), [React](https://facebook.github.io/react/), and [Vue](https://vuejs.org/) that have an ASP.NET Core backend. These templates:
7+
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:
88

99
* Create a Visual Studio solution with a frontend project and a backend project.
1010
* Use the Visual Studio project type for JavaScript and TypeScript (*.esproj*) for the frontend.

aspnetcore/release-notes/aspnetcore-8.0.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -871,7 +871,7 @@ The following sections describe miscellaneous new features in ASP.NET Core 8.
871871

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

874-
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.io/), [React](https://facebook.github.io/react/), and [Vue](https://vuejs.org/). These templates:
874+
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:
875875
876876
* Create a Visual Studio solution with a frontend project and a backend project.
877877
* Use the Visual Studio project type for JavaScript and TypeScript (*.esproj*) for the frontend.

aspnetcore/security/anti-request-forgery.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -189,7 +189,7 @@ For more information, see <xref:Microsoft.AspNetCore.Builder.CookieAuthenticatio
189189

190190
:::code language="csharp" source="anti-request-forgery/samples/6.x/AntiRequestForgerySample/Program.cs" id="snippet_Middleware" highlight="5,7-20":::
191191

192-
The preceding example sets a cookie named `XSRF-TOKEN`. The client can read this cookie and provide its value as a header attached to AJAX requests. For example, Angular includes [built-in XSRF protection](https://angular.io/guide/http#security-xsrf-protection) that reads a cookie named `XSRF-TOKEN` by default.
192+
The preceding example sets a cookie named `XSRF-TOKEN`. The client can read this cookie and provide its value as a header attached to AJAX requests. For example, Angular includes [built-in XSRF protection](https://angular.dev/best-practices/security#httpclient-xsrf-csrf-security) that reads a cookie named `XSRF-TOKEN` by default.
193193

194194
### Require antiforgery validation
195195

@@ -510,7 +510,7 @@ For more information, see <xref:Microsoft.AspNetCore.Builder.CookieAuthenticatio
510510

511511
:::code language="csharp" source="anti-request-forgery/samples/6.x/AntiRequestForgerySample/Program.cs" id="snippet_Middleware" highlight="5,7-20":::
512512

513-
The preceding example sets a cookie named `XSRF-TOKEN`. The client can read this cookie and provide its value as a header attached to AJAX requests. For example, Angular includes [built-in XSRF protection](https://angular.io/guide/http#security-xsrf-protection) that reads a cookie named `XSRF-TOKEN` by default.
513+
The preceding example sets a cookie named `XSRF-TOKEN`. The client can read this cookie and provide its value as a header attached to AJAX requests. For example, Angular includes [built-in XSRF protection](https://angular.dev/best-practices/security#httpclient-xsrf-csrf-security) that reads a cookie named `XSRF-TOKEN` by default.
514514

515515
### Require antiforgery validation
516516

@@ -782,7 +782,7 @@ For more information, see <xref:Microsoft.AspNetCore.Builder.CookieAuthenticatio
782782

783783
:::code language="csharp" source="anti-request-forgery/samples/6.x/AntiRequestForgerySample/Program.cs" id="snippet_Middleware" highlight="5,7-20":::
784784

785-
The preceding example sets a cookie named `XSRF-TOKEN`. The client can read this cookie and provide its value as a header attached to AJAX requests. For example, Angular includes [built-in XSRF protection](https://angular.io/guide/http#security-xsrf-protection) that reads a cookie named `XSRF-TOKEN` by default.
785+
The preceding example sets a cookie named `XSRF-TOKEN`. The client can read this cookie and provide its value as a header attached to AJAX requests. For example, Angular includes [built-in XSRF protection](https://angular.dev/best-practices/security#httpclient-xsrf-csrf-security) that reads a cookie named `XSRF-TOKEN` by default.
786786

787787
### Require antiforgery validation
788788

aspnetcore/security/authorization/limitingidentitybyscheme/samples/AuthScheme/ClientApp/src/app/home/home.component.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ <h1>Hello, world!</h1>
22
<p>Welcome to your new single-page application, built with:</p>
33
<ul>
44
<li><a href='https://get.asp.net/'>ASP.NET Core</a> and <a href='https://msdn.microsoft.com/en-us/library/67ef8sbd.aspx'>C#</a> for cross-platform server-side code</li>
5-
<li><a href='https://angular.io/'>Angular</a> and <a href='http://www.typescriptlang.org/'>TypeScript</a> for client-side code</li>
5+
<li><a href='https://angular.dev/'>Angular</a> and <a href='http://www.typescriptlang.org/'>TypeScript</a> for client-side code</li>
66
<li><a href='http://getbootstrap.com/'>Bootstrap</a> for layout and styling</li>
77
</ul>
88
<p>To help you get started, we've also set up:</p>

aspnetcore/tutorials/choose-web-ui.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ To get started with ASP.NET Core MVC, see <xref:tutorials/first-mvc-app/start-m
6161

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

64-
Build client-side logic for ASP.NET Core apps using popular JavaScript frameworks, like [Angular](https://angular.io/), [React](https://facebook.github.io/react/), 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.
64+
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.
6565

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

aspnetcore/tutorials/choose-web-ui/includes/choose-web-ui3-7.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ To get started with ASP.NET Core MVC, see <xref:tutorials/first-mvc-app/start-m
4949

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

52-
Build client-side logic for ASP.NET Core apps using popular JavaScript frameworks, like [Angular](https://angular.io/), [React](https://facebook.github.io/react/), 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.
52+
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.
5353

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

0 commit comments

Comments
 (0)