ASP.NET Core and SPAs in. NET 6

Summary

We will be introducing a new experience for SPA templates in .NET 6 timeframe. This experience is going to focus on decoupling the frontend from the backend into two separate projects.

Motivations and goals

Motivation: Easily enable users to update their Angular and Reacts versions as well as keep up with the latest SPA template.
Goal: Providing flexibility to our community to bring in new templates or update the existing SPA template without having to rely on .NET Core SDK.

This would open the following:

• Bring your own SPA(BYOSPA) | Simplifying using ASP.NET Core with more SPA frameworks. The JavaScript SPA frameworks ecosystem is growing, and we want to enable the community easily to use the SPA template of their choice.

• Up-to-date templates: Keep up with the latest versions for your preferred SPA framework.

• Community templates: enable and encourage community participation to update and bring their own templates to the ecosystem.

What to expect

• Proxy through the SPA frameworks dev server: Leverage the webpack dev server proxy approach available Preview 4.
  With new proxy work when you ran an app it will start the ASP.NET Process and the process will check if the JS SPA dev server running and start it if it’s not and your app will run.
  
  

• A new template repo: We will be moving all the JS SPA Frameworks to a new repo in Preview 5 and updates the React and Angular templates.

• New tooling for JavaScript/TypeScript in Visual Studio: unit testing, a GUI npm management, CLI based templates and more to be announced. This work is being done by the Microsoft TypeScript and JavaScript team; current date of availability is June 15.

• Separating the Client App and Server App into separate projects in one solution. Below is prototype of experience we are working towards. Date for this work to be completed by June.