Difference between MVC & Angular symbiotic project, vs. them being separate? #818

New Issue

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

fergalmoran commented

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

Originally created by @RobertPaulson90 on 4/20/2017

What specific advantages would I get from generating a MVC+Angular integrated project via. yo aspnetcore-spa, as opposed to using a pure angular boilerplate in a separate project, but it talking with my REST MVC Web-api's backend running by itself?

I've been working on an MVC project with basic views, but would like to spike out for an angular frontend.
I know I can simply consume my MVC REST web-api's from angular, but what exactly am I losing as opposed to doing everything over in a fully integrated angular & mvc single project.

Is it simply a quesiton of ease of life? Press F5 to launch both back- and frontend?

*Originally created by @RobertPaulson90 on 4/20/2017* What specific advantages would I get from generating a MVC+Angular integrated project via. yo aspnetcore-spa, as opposed to using a pure [angular boilerplate](https://github.com/AngularClass/angular2-webpack-starter) in a separate project, but it talking with my REST MVC Web-api's backend running by itself? I've been working on an MVC project with basic views, but would like to spike out for an angular frontend. I know I can simply consume my MVC REST web-api's from angular, but what exactly am I losing as opposed to doing everything over in a fully integrated angular & mvc single project. Is it simply a quesiton of ease of life? Press F5 to launch both back- and frontend?

fergalmoran closed this issue

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

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#818