I've been researching for a few hours but because I'm late to the game a lot of what I find are old q&a's (7 yrs old) so I figured I'd lean on this community for some current guidance.

More than 10 years ago I inherited and continue to build and maintain an ASP.NET WebForms website (not application) critical to our organization. It is a reasonably large site coming in at around 400 aspx pages (but only 200 appear to be regularly used anymore). In that solution are 3 projects: the first being the website, and the other two projects are just code (the business and data layers).

We are a manufacturer, and the site tracks the parts we build, the orders we receive, generates invoices, schedules and tracks production, material usage, etc. The point is it's a boring corporate app that doesn't require any flashy client-side features; its almost entirely forms to get info, and grids of data for reporting with the occasional chart thrown in. LOTS of business logic, though!

We need to upgrade/replace the WebForms website in more modern technology(s). We are a Microsoft shop and I'd be the only developer working on this. I have a DevExpress universal subscription which has proven invaluable. It appears MVC is a no-go because "it is no longer in active development". Blazor and its SPA doesn't seem like an appropriate technology to migrate to when I've got such a large website. So I feel like I'm left with Razor. Am I on the right track here?

CodePudding user response：

It appears Blazor is a perfectly good replacement for my large Webforms solution. I got tripped up with ignorance around what a SPA (single page application) is all about (especially since I didn't get experience with routing while in Webforms and I'm leapfrogging MVC where I expect the concept was introduced). I'd have marked someone else's comment as an answer if I could.

CodePudding user response：

What I did for my old ASP.NET site is to create a subdomain in IIS for the Blazor stuff, and to move things over section by section. That way, I didn't have to re-create hundreds of pages before users could start benefitting from the improvements in responsiveness.