Preserving SPA tool chains (e.g. Angular CLI) #829

New Issue

fergalmoran · 2025-08-09T17:17:50Z

fergalmoran commented

2025-08-09 17:17:50 +00:00

Originally created by @smoses2 on 4/15/2017

I know several asked how to specifically integrate angular CLI into the template:
2/14 blog announcement. It has also been mentioned as part of other issue threads on GitHub (https://github.com/aspnet/JavaScriptServices/issues/97).

I use Angular CLI and asp.net core, and really like the idea of these templates integrating the asp client-server and the associated tooling you've developed. But removing the spa/client native tooling such as Angular CLI is a deal breaker for me. I do not use React/Redux, but I would imagine there may be similar issues.

I have seen several options for this, and I like the idea of this 2 project solution:
Angular2 CLI with ASP.NET Core application - tutorial

Here, the asp.net core backend has one project, and the spa frontend another. The build process for the spa frontend writes distribution to the wwwroot folder of the asp.net core application.

Currently, the template is not useful to me other than a demo. In the future, I hope these templates can be my starter projects, once they leverage the SPA framework functionality, while still facilitating asp.net core - spa integration/build/CI.

*Originally created by @smoses2 on 4/15/2017* I know several asked how to specifically integrate angular CLI into the template: [2/14 blog announcement](https://blogs.msdn.microsoft.com/webdev/2017/02/14/building-single-page-applications-on-asp-net-core-with-javascriptservices/). It has also been mentioned as part of other issue threads on GitHub (https://github.com/aspnet/JavaScriptServices/issues/97). I use Angular CLI and asp.net core, and really like the idea of these templates integrating the asp client-server and the associated tooling you've developed. But removing the spa/client native tooling such as Angular CLI is a deal breaker for me. I do not use React/Redux, but I would imagine there may be similar issues. I have seen several options for this, and I like the idea of this 2 project solution: [Angular2 CLI with ASP.NET Core application - tutorial](https://devblog.dymel.pl/2016/10/25/angular2-cli-with-aspnet-core-application-tutorial/) Here, the asp.net core backend has one project, and the spa frontend another. The build process for the spa frontend writes distribution to the wwwroot folder of the asp.net core application. Currently, the template is not useful to me other than a demo. In the future, I hope these templates can be my starter projects, once they leverage the SPA framework functionality, while still facilitating asp.net core - spa integration/build/CI.

fergalmoran closed this issue

2025-08-09 17:17:50 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#829