asp.net - MVC vs WebForms in my production environment -


over past couple weeks i've been examining mvc 4.0 , trying see whether or not make switch web forms mvc.

my current production environment is: 1) 1 master database, 3 separate asp.net web form applications (a scheduler, sales reporting, central administration) communicate 2) master database not contain appropriate foreign keys, uses lot of stored procedures current applications, structure use re-designing its' i've inherited legacy systems & code.

as started created prototype improved sales reporting application started running issues had continually make modifications database using migration tool in visual studio. found relationship between tables not correctly established, it's been more challenging using entity framework.

i no means mvc expert , entity framework expert, i've started question whether should jump mvc existing situation. scares me amount of database changes i've had make in test environment enable proper models controller , views. me making these changes, feel other 3 web form applications have re-tested don't have resources for. cannot afford go wrong in master database or web form apps because client facing.

i don't mind learning curve of mvc, find quite interesting, manager not care use, , isn't opposed me learning extension of asp.net. suppose there timeline in place, not concrete.

i'm reaching out others may have faced similar scenario. concerns valid? should stick web form application or should push forward mvc world?

depends on how separated layers of application are. if have solid service layer handles of data access , passes domain objects , forth, conversion mvc not bad. feasible have mvc front end on standard ado.net end.

based on structure of database, trying use ef going difficult unless proper constraints put place. ef won't work unless database set properly.

if want move mvc recommend doing in stages.

  1. separate ui layer service layer if not already.
  2. convert ui layer mvc.
  3. when happy ui, can start making database changes , convert data access layer ef.

while converting ui mvc, create models replicate database tables , pass ui instead of directly pulling back. way when convert ef, have correct models in place , ui layer unaffected changes


Comments

Popular posts from this blog

c# - DetailsView in ASP.Net - How to add another column on the side/add a control in each row? -

javascript - firefox memory leak -

Trying to import CSV file to a SQL Server database using asp.net and c# - can't find what I'm missing -