Business decision about mvc vs webforms for Web Based Intranet database systems
Posted on 2015-02-24
I've got a business decision to make, and I need the advice of some experts. - where better to go?
I've been making web-based intranet database systems since the late 90's. I started by converting an Access database system to classic ASP. (c# wasn't even in the picture at the time)
Later, I converted those systems to .Net webforms - yes, using the evil VB.net that nobody uses but me and my 3 developers.
Anyway, I sold a big ERP system to a company called Intellievent and they've been pretty successful with it, but they only have a license for the Event industry. We still own the copyright and rights to sell to other industries.
Here's the problem: No matter what industry we target, there's going to have to be a lot of changes. The first step I'm going to make is to redo all the code in C#, just to make it easier to find staff and increase resale value.
Now, everybody keeps telling me to convert it to MVC, which is a HUGE change, but I am considering. So, here's the "thing". My initial tests with MVC were pretty good. I can see how easily I could redo the websites, but the CRUD needs seem like they are really a pain in the butt. We do almost all validation both client-side and server side. Not having a view-state is a pain, but not overwhelming, but doing all the validation and then CRUD via controllers looks to be a pain in the butt - at least from a webforms->MVC workload point of view.
To me, after a week of MVC testing (it's all new to me), it seems like the "slowness" of webforms is negated by the fact that an intranet has almost no load. It seems that the time-saved by MVC from an organizational standpoint really isn't much if you've got all your class objects separated anyway.
So, I have about a week before I need to start mapping out the development of our new product. And I want to make 100% sure that MVC is or is not worth the investment.