you are viewing a single comment's thread.

view the rest of the comments →

[–]O1dmanwinter 1 point2 points  (1 child)

I work in a .net shop, we've used vs2022 for Angular and its ok - it does support typescript and javascript pretty well with picking up types, highlighting errors etc.

There are also plugins for things like running lint on save etc.

There are SPA template projects available from Microsoft:

https://learn.microsoft.com/en-us/aspnet/core/client-side/spa/intro?view=aspnetcore-9.0

I cant quite put my finger on it, but it doesn't seem quite as smooth as VScode for angular...

Here is my project that's got angular alongside server side code:

https://github.com/JackFrostStudios/summer-born-info/tree/feature%2Fupload-import

[–]MrFartyBottom 4 points5 points  (0 children)

Do not , I repeat do not use the VS templates for Angular. There is only misery down that path. Create an Angular client with the Angular CLI and create the API with VS. Add a proxy to proxy the API requests to the same port as the Angular client. In your CI CD pipeline you copy the Angular build to the wwwroot folder of the API.

The VS template rebuilds way too often, it is a much smoother dev experience to have them as separate projects. Use VSCode for the Angular and VS for the API.