have you moved away from using React with .NET MVC for a particular reason or have you just become interested in other things?
Tooling support for classic ASP.NET MVC (I haven't used ASP.NET Core) has been subpar (hot reloading was buggy, requireing manual refresh & new JavaScript syntax was flagged as erroneous, etc).
And also following JamStack, having a separate API server with a pure React front-end helped to separate responsibilities.
I can't seem to find the post(was it a forum?) now, but MS wasn't focusing on making SPA easier to develop few years ago so I moved away.
Thanks for your perspective on this. Hoping to make the switch to .NET Core sometime soon and it seems like it is better suited, going to the Live 360 conference later this month and will hopefully get more information. Have a good one!
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.
Hi Tory, check out the replies below.
Tooling support for classic ASP.NET MVC (I haven't used ASP.NET Core) has been subpar (hot reloading was buggy, requireing manual refresh & new JavaScript syntax was flagged as erroneous, etc).
And also following JamStack, having a separate API server with a pure React front-end helped to separate responsibilities.
I can't seem to find the post(was it a forum?) now, but MS wasn't focusing on making SPA easier to develop few years ago so I moved away.
Thanks for your perspective on this. Hoping to make the switch to .NET Core sometime soon and it seems like it is better suited, going to the Live 360 conference later this month and will hopefully get more information. Have a good one!