Changing the View Engine in Asp.NET MVC -


i trying learn asp.net mvc porting current app written in asp.net webforms mvc. starters, planning use default view engine (webformsviewengine) tutorials/examples , book have use default.

however, know sure not want use webformviewengine in future , once have grasp of mvc, switch different viewengine (spark seems interesting)

would simple change or take lot of effort in terms of coding new views? want know involve more effort? learning alternate viewengine or switching later?

ok - firstly you've got decent sized investment in webforms i'm assuming, , virtue of that, you'll have fair amount of user controls on existing forms etc. i'm sure know in going work in process, , has nothing view engine choose because webforms mvc view engine doesn't support user controls directly. part of work still need done regardless...

secondly, looking view engine can take most of other view built in logic , code (i.e not user controls), , mean stuff between bee-stings ( <%= blah %> ).

obviously webforms view engine support same syntax, don't want use default webforms view engine. you'll happy know spark supports <%= blah %> syntax, , has been done support migrations this.

your best bet before deciding watch this recent video here, , see how louis goes through simple webforms-based mvc solution , keeps running correctly though code still contains <%= blah %> syntax.

this support makes easier transition , when you're ready can start moving code more recommended way of using ${blah} syntax instead. can done @ own pace whilst overall functionality still works.

hope helps,

all best,

rob g


Comments

Popular posts from this blog

android - Spacing between the stars of a rating bar? -

html - Instapaper-like algorithm -

c# - How to execute a particular part of code asynchronously in a class -