Angular and ASP.NET Core Template fails on creation

[PanzerFowst]

This should be fixed in VS 17.8.1 and working for all versions of Angular. Are you still seeing the issue after installing the latest? /cc @PranavSenthilnathan

Originally posted by @joj in #52049

Bug

This issue happens again with Angular 20.0.1.

Temporary fix

Installing Angular 19 fixes this error:

npm install -g @angular/cli@v19

[jerricko]

This issue is the result of Angular changing their naming scheme in v20. They no longer do app.component.ts or app.module.ts and instead do app.ts and app-module.ts. The template creation fails when it looks for app.component.ts when @angular/cli v20 is installed.

[PanzerFowst]

I wonder if adding a dropdown for what version of Angular along with what version of .NET when making a project with this template would help?

At least, it would help people realize that Angular versions matter I feel like... (I bumped into this just trying to update / build an internal tool with no experience of Angular beforehand.)

[wtgodbe]

@BrennanConroy do you know anything about this one? Do we own the aspnetcore npm template?

[netdragonboberb]

This is still happening with VS 17.14.12

[danmoseley]

@mackinnon where are these templates? I do not see them in aspnetcore

[danmoseley]

We need to find the right owner for this

[MackinnonBuck]

@joj, your team owns these templates, correct?

[joj]

Yep. I believe this issue is fixed already, but the fix has not yet been released.

[danmoseley]

Can this issue move to the right repo (what is that? SDK?)

[joj]

We track internally. If you want to close this as tracked that's fine. This is the closest we have to an external link for it: https://developercommunity.visualstudio.com/t/Creating-a-new-Solution-with-Angular-is-/10918866

Edit: better feedback item with a workaround

[MackinnonBuck]

Thanks, @joj! Closing this out, as it's being tracked externally.