title: Advantages using the Yeoman .net core spa Angular template to create an Angular MVC project if API is a separate project?
body: <p>I created a typical N-Tier architecture solution with project called TestProj.Api, TestProj.Business, TestProj.Data. All 3 of these projects work great together in VS2017.</p>
  
  <p>Then I added a fourth project using the Yeoman Angular .Net Core Spa Template: TestProj.Web. This project makes api calls to TestProj.Api with CORS. I currently run multiple solution startup projects: TestProj.Api and TestProj.Web.</p>
  
  <p>I am starting to notice that I like developing Angular in VSCode and additionally not sure if I like the Angular ASP.NET Core Template. I am wondering if TestProj.Web should be created outside of my solution.</p>
  
  <p>What are the true advantages of using this Angular Template, here are the ones I can think of:<br>
  1. Able to keep everything in same VS2017 solution. Api, Business, Data, Web<br>
  2. Able to have a server-side Api and Angular in the same project (which I am not taking advantage of since I want my API to be completely separate)</p>
  
  <p>Is there anything else I am not thinking of? Is there any suggestions on what I should do?</p>