asp.net mvc - MVC vs ASPX dynamic page render -
i have cms website written in aspx 2.0 allows users build pages dropping controls on page , setting properties (reflection on server side) , events (client side js). render engine knows property call on each control find out save database. went through pitfalls of control re-hydration , lack of proper ids on controls , struggled make solution seo friendly partial @ best. suffer viewstate getting huge have started @ mvc better way forwards next version. final design of page set when user decides promote live, , may make many changes per day.
a typical page may have many textbox controls, radio button groups, checkbox groups, dropdownlists , images. have few of our own controls reflect @ runtime solution.
from initial research mvc, looks have been written avoid these types of issues , not try hide html looks promising giving final markup more cross browser friendly.
now question - since requirements generate dynamic pages dynamic html controls, step far mvc , should stick aspx, or there way generate dynamic content suitable non technical person able do?
really appreciate guidance before jump in both feet :)
thanks
mark
some of main advantages of mvc: clean html, no viewstate written on page, easier support html5 , seo well.
for me, since used mvc 3 years ago don't want touch webforms thesedays.
btw, if want cms + mvc, why not use orchard rather building yourself?
Comments
Post a Comment