Well it looks like I may be forced to build a new system in webforms after havin
ID: 651460 • Letter: W
Question
Well it looks like I may be forced to build a new system in webforms after having worked exclusively in MVC for the last 3 years.
Initially I didnt think this was going to be a problem except the application calls for a very large amount of ajax and rich client-side interaction, (think GMail or Facebook).
Back when I was doing heavy WebForms development we were only doing small amounts of ajax. I remember AJAX update panels being an absolute nightmare. I remember I ended up using mostly straight html and using JQuery to hit ASHX handlers.
Basically I know good clean ways of doing almost everything with MVC.Net but having to use WebControls and having seperate webpages everywhere seems like a night mare to me.
Does anyone know any good resources for going from MVC.Net to WebForms? Seems like a completely idiotic thing to do in my opinion but I planning for the worst.
Explanation / Answer
In short: your situation is really strange/not common, as the vice-verse is more usual case nowadays. However, what you may do might be the utilization of improvements in ASP.NET WebForms framework starting from 4.0.
A good place to start would be - ASP.NET 4 and Visual Studio 2010 Web Development Overview , just to sharpen-up your memory.
In addition, ViewStateMode is something that you would want to so spend some time - Exploring ASP.NET 4.0
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.