Tutorial: Create an ASP.NET Core app with Angular in Visual Studio

Applies to: Visual Studio Visual Studio for Mac Visual Studio Code

In this article, you learn how to build an ASP.NET Core project to act as an API backend and an Angular project to act as the UI.

Currently, Visual Studio includes ASP.NET Core Single Page Application (SPA) templates that support Angular and React. The templates provide a built-in Client App folder in your ASP.NET Core projects that contains the base files and folders of each framework.

You can use the method described in this article to create ASP.NET Core Single Page Applications that:

• Put the client app in a separate project, outside from the ASP.NET Core project
• Create the client project based on the framework CLI installed on your computer

Note

A simplified, updated template is available starting in Visual Studio 2022 version 17.5. This template creates two projects in the initial solution and eliminates several configuration steps compared to the previous template. This article describes the project creation process using the new template.

Prerequisites

Make sure to install the following:

• Visual Studio 2022 version 17.5 or later with the ASP.NET and web development workload installed. Go to the Visual Studio downloads page to install it for free. If you need to install the workload and already have Visual Studio, go to Tools > Get Tools and Features..., which opens the Visual Studio Installer. Choose the ASP.NET and web development workload, then choose Modify.
• npm (https://www.npmjs.com/), which is included with Node.js
• Angular CLI (https://angular.io/cli) This can be the version of your choice

Create the frontend app

1. In the Start window (choose File > Start Window to open), select Create a new project.

   

2. Search for Angular in the search bar at the top and then select Angular and ASP.NET Core (Preview).

   

3. Give your project and solution a name, and choose Create.

   Once the project is created, Solution Explorer should look like this:

   

   Compared to the standalone Angular template, you see some new and modified files for integration with ASP.NET Core:

   • aspnetcore-https.js
   • proxy.js
   • package.json(modified)
   • angular.json(modified)
   • app.components.ts
   • app.module.ts

Set the project properties

1. In Solution Explorer, right-click the ASP.NET Core project and choose Properties.

   

2. Go to the Debug menu and select Open debug launch profiles UI option. Uncheck the Launch Browser option.

   

   This prevents opening the web page with the source weather data.

   Note

   launch.json stores the startup settings associated with the Start button in the Debug toolbar. Currently, launch.json must be located under the .vscode folder.

Start the project

To start the project, press F5 or select the Start button at the top of the window. You will see two command prompts appear:

• The ASP.NET Core API project running
• The Angular CLI running the ng start command

Note

Check console output for messages, such as a message instructing you to update your version of Node.js.

You should see an Angular app appear, that is populated via the API. If you don't see the app, see Troubleshooting.

Publish the project

Starting in Visual Studio 2022 version 17.3, you can publish the integrated solution using the Visual Studio Publish tool.

Note

To use publish, create your JavaScript project using Visual Studio 2022 version 17.3 or later.

1. In Solution Explorer, right-click the ASP.NET Core project and choose Add > Project Reference.

2. Select the Angular project and choose OK.

3. Right-click the ASP.NET Core project in Solution Explorer and choose Unload Project.

   This opens the .csproj file for the project.

4. In the .csproj file, update the project reference and add <ReferenceOutputAssembly> with the value set to false.

   When you've updated the reference, it should look like this (substituting your own project folder and project name).

   <ProjectReference Include="..\angularprojectfolder\angularprojectname.esproj">
       <ReferenceOutputAssembly>false</ReferenceOutputAssembly>
   </ProjectReference>
   

5. Right.click the ASP.NET Core project and choose Reload Project.

6. In Program.cs, update the check for Environment.IsDevelopment so it looks like the following.

   // Configure the HTTP request pipeline.
   if (app.Environment.IsDevelopment())
   {
      app.UseSwagger();
      app.UseSwaggerUI();
   }
   else
   {
      app.UseDefaultFiles();
      app.UseStaticFiles();
   }
   

7. To publish, right click the ASP.NET Core project, choose Publish, and select options to match your desired publish scenario, such as Azure, publish to a folder, et al.

   The publish process takes more time than it does for just an ASP.NET Core project, since the npm run build command gets invoked when publishing.

   You can modify the npm run build command using the Production Build Command in the Angular project properties. To modify it, right-click the Angular project in Solution Explorer and choose Properties.

Troubleshooting

Proxy error

You may see the following error:

[HPM] Error occurred while trying to proxy request /weatherforecast from localhost:4200 to https://localhost:5001 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)

If you see this issue, most likely the frontend started before the backend. Once you see the backend command prompt up and running, just refresh the Angular App in the browser.

Verify port

If the weather data does not load correctly, you may also need to verify that your ports are correct.

1. Go to the launchSettings.json file in your ASP.NET Core project (in the Properties folder). Get the port number from the applicationUrl property.

   If there are multiple applicationUrl properties, look for one using an https endpoint. It should look similar to https://localhost:7049.

2. Then, go to the proxy.conf.js file for your Angular project (look in the src folder). Update the target property to match the applicationUrl property in launchSettings.json. When you update it, that value should look similar to this:

   target: 'https://localhost:7049',