You say implementing the Angular app inside ASP.Net Core "seems to be a common approach". I've had experiences w/Angular bootcamps and onsite adoptions that found it uncommon. The middleware hooks are handy, but totally handle-able by the Angular componentry as well. I could see .Net devs not willing to let go of their stack and knee-jerk reacting by making every site an ASP.Net site. I'd also consider some of the Authorize handlers & policies, but then it starts to bleed right into a position I've held against the Angular wave...why not just use MVC Views with a 2-way binding and SPA routing lib instead of Angular (CLI). I guess I'm not sold. Are there any better reasons to do this than the middleware and other lifecycle event hooks?
Currently working as a contractor, mostly on Node.js and Typescript, also React.
Also have a background in academia, I have a PhD in CS and worked as a researcher in AI.
I don't think it's a good idea at all and I think you are probably right about it being a knee jerk reaction of making every website an ASP.NET website, even if it's mostly serving just static HTML and JavaScript
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You say implementing the Angular app inside ASP.Net Core "seems to be a common approach". I've had experiences w/Angular bootcamps and onsite adoptions that found it uncommon. The middleware hooks are handy, but totally handle-able by the Angular componentry as well. I could see .Net devs not willing to let go of their stack and knee-jerk reacting by making every site an ASP.Net site. I'd also consider some of the Authorize handlers & policies, but then it starts to bleed right into a position I've held against the Angular wave...why not just use MVC Views with a 2-way binding and SPA routing lib instead of Angular (CLI). I guess I'm not sold. Are there any better reasons to do this than the middleware and other lifecycle event hooks?
I don't think it's a good idea at all and I think you are probably right about it being a knee jerk reaction of making every website an ASP.NET website, even if it's mostly serving just static HTML and JavaScript