IMPORTANT!
This forum is now archived. Click here for the New Support Forum
Pro: CLI not setup in VS?
Quote from Jonathon Wyza on February 4, 2018, 9:26 pmIs there a reason why the angular CLI config file doesn't exist for the VS version of the app? It seems to only exist in the stand-alone folder, which is kind of useless for a single combined solution.
Is there a reason why the angular CLI config file doesn't exist for the VS version of the app? It seems to only exist in the stand-alone folder, which is kind of useless for a single combined solution.
Quote from Eben Monney on February 5, 2018, 6:04 amThe VS version does not use angular cli but uses msbuild/webpack/IIS, IIS Express (or whatever you setup) to give you a unified backend/frontend workflow.
With this configuration both the client and server exists in the same project and are served with a single Web Server. This is the same architecture other default .NET project uses as opposed to a separate server/project for client and another to serve the backend.
This option is appreciated by the typical .NET developer who uses VisualStudio or VisualStudio Code.
There is work by microsoft to integrate Angular CLI into this workflow. This is still in the early stages and this project will be updated once that work is matured enough.
If you prefer to use the Angular CLI version you'll need to launch that separately using "npm start". This is the traditional way of working with Angular CLI applications.
The VS version does not use angular cli but uses msbuild/webpack/IIS, IIS Express (or whatever you setup) to give you a unified backend/frontend workflow.
With this configuration both the client and server exists in the same project and are served with a single Web Server. This is the same architecture other default .NET project uses as opposed to a separate server/project for client and another to serve the backend.
This option is appreciated by the typical .NET developer who uses VisualStudio or VisualStudio Code.
There is work by microsoft to integrate Angular CLI into this workflow. This is still in the early stages and this project will be updated once that work is matured enough.
If you prefer to use the Angular CLI version you'll need to launch that separately using "npm start". This is the traditional way of working with Angular CLI applications.
IMPORTANT!
This forum is now archived. Click here for the New Support Forum