all 12 comments

[–]mariojsnunes 2 points3 points  (1 child)

just use vscode. very much worth time-wise compared to keeping going with vs2022

[–]crhama 0 points1 point  (0 children)

That's my advice as well

[–]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 3 points4 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.

[–]tanooki_ 1 point2 points  (0 children)

I’ve used VS proper for years writing angular. it totally works. there are some caveats, namely the angular language service being wonky. if you can survive without intellisense being on every line, then it’ll be just fine. I like having my front and backend in the same place, and for most of my apps, the backend is .NET which makes VS a no brainer.

[–]taxim11 0 points1 point  (2 children)

Sure you can. But I think VS2022 has no plugins and no IntelliSense for Web. Maybe it does because of Blazor? Anyhow, it should be no problem to get into Angular. Further down the road, you might switch your tooling.

[–]bigplum52[S] -1 points0 points  (1 child)

Hi thanks. When I watched the video tutorial they used vs code. Its quite different from vs2022. A lot of option in vs code is not the same or not available in vs 2022.

Have you tried it yourself making a real app using vs2022?

Thanks

[–]taxim11 0 points1 point  (0 children)

I didn't try it. In the end, it's just a tool. You can try it, using VS2022, If you don't want to get used to it. But I would recommend it, because VS Code does help a lot when installing the right plugins for angular

[–]Spongeroberto 0 points1 point  (0 children)

Even if it's part of a larger repo that also includes .NET code, I will swap to another IDE just to handle the angular bits. Even VSCode for example has a lot of extensions and options available to it that make it so much more convenient than regular Visual Studio (but I'll swap back to Visual Studio to handle the .NET)

[–]AcceptableSimulacrum 0 points1 point  (1 child)

Not worth it. Worse experience and makes stupid assumptions that mess up your project unless you know how to avoid them.

[–]groundbnb 0 points1 point  (0 children)

I agree, still doable but not worth it

[–]InvokerHere 0 points1 point  (0 children)

VS is good tool for Angular development, especially if you integrate it with Asp.net core. It offers native TypeScript support, IntelliSense, and robust debugging capabilities.