I am using dot-net for my back-end and angular for my front-end. Until now I used to create both front and back-end separately. Of course I should take care of Cross-origin issue, so the front-end can communicate with back-end. Lately I used the (ASP.Net Core With Angular) template, and instead of separately creating my angular project. I created it within my back-end solution as a project. In this template you see that Visual Studio create an Angular project for you with some extra files and provide you directly a Controller folder. In this template project, you see a proxy in a file named: (proxy.conf.js) and you can call your back-end without Cross-origin issue. However I read that this is only for local tests. It use a server and this saver is based on the Webpack dev server. I read it from this article: https://juristr.com/blog/2016/11/configure-proxy-api-angular-cli/
I am intended to host my solution later in Azure in a Webapp.
My questions: 1- Which approach is the better one, creating a separate Angular project and host it separately or using the (ASP.Net Core With Angular) template from Visual Studio? and why?
2- Assume I use the (ASP.Net Core With Angular) template, in this case the proxy is only for local test, right? If yes, do you think it is a good idea to remove the proxy and for local test as well as later in cloud use Cross-origin policy in my back-end?