Search code examples
asp.net.netasp.net-mvcwebformsviewstate

Can ASP.NET state management be daunting for beginners?


To all you ASP.NET experts and beginners, do you look at a state management as a difficult and annoying task to do? If you were to start over with ASP.NET would you consider ASP.NET MVC and never have to deal with ViewState again?

Also , is it true that once you go ASP.NET MVC you never go back to ASP.NET Webforms (Unless of course your job requires that)?


Solution

  • ViewState isn't daunting for beginners, it's daunting for experts. ViewState is awesome because it obfuscates state management away for beginner programmers and allows them to focus on writing code. It then comes back to haunt them later when they need to write something more advanced and realize ViewState has severe limitations and drawbacks but that they don't know how to do anything else.

    As for ASP.NET WebForms, I must admit I first abandoned it entirely in favor of ASP.NET MVC (aside from supporting some legacy apps) but have recently found myself returning to ASP.NET for smaller projects. If I need something quick-and-dirty I generally turn to WebForms. If it's something larger that I'm going to have to maintain down the road I find MVC more appealing.