blog

blog copied to clipboard

Written on 16.01.2018 07:37:57

URL: http://asp.net-hacker.rocks/2018/01/15/aspnetcore-angular-review.html

Comment written by Andrew Lewis on 16.01.2018 15:53:14

I’m curious why would wouldn’t use the SPA template for large sites? Do you have an article or links that explain the reasoning behind this, or when the ng5/core template isn’t appropriate?

Comment written by Jürgen Gutsch on 16.01.2018 17:17:20

Because you always need to hack a little bit around the typescript config, npm, webpack, etc. to get it running in VS. Some of those technologies used with Angular are not made for VS. I would also separate backend and frontend into two separate projects, because than this projects can scale separately. I would also separate the hosting of the both parts on different websites. Doing this also the hosting can scale separately.
From the development perspective, you would be able to hier a frontend developer, who doesn't know VS.

Comment written by Mauricio Bacelis on 20.02.2018 04:33:59

when i create my project on visual studio, my project is created with the 4 version of angular. anyone know why is this happening? i have the last version of visual studio, net core sdk, node.js, etc. I have all updated

Comment written by Jürgen Gutsch on 20.02.2018 07:47:49

Ciao Mauricio,
this is just because it is defined like this in the Visual Studio project templates. Usually the templates are a little older. If you want to use Angular 5, you only need to update the package.json

Comment written by Andrey Kuznetsov on 29.03.2018 22:01:04

Not really. The webpack config need to be chaned as well. Angular 5 uses a different way of compilation.

Comment written by Jürgen Gutsch on 30.03.2018 23:12:38

Thanks for that hint :-)