One of the major reasons for using webforms is the ease of being able to maintain viewstate. I would like to build an asp.net mvc application so what options do I have for maintaining viewstate?
Kind regards
One of the major reasons for using webforms is the ease of being able to maintain viewstate. I would like to build an asp.net mvc application so what options do I have for maintaining viewstate?
Kind regards
Due to its basic design of maintaining the business layer separate from presentation layer, MVC Framework does not allows to preserve the State over HTTP, However Cookies, Serializable classes,ViewData and ViewBag are good ways to preserve the state in MVC.
If you're wanting to make for example, a Wizard styled form, you could create a Serializable class to retain the viewstate:
You could then serialize this class and use it in a similar way to using ViewState (as a hidden field in the form).
You can imitate view state by serializing model in view using MVC3Futures project
All you have to do is to serialize model and encrypt it in view.
And in controller add deserialized attribute.
ASP.NET MVC does not use ViewState in the traditional sense (that of storing the values of controls in the web page). Rather, the values of the controls are posted to a controller method. Once the controller method has been called, what you do with those values is up to you.
ASP.NET MVC will persist the values of the controls long enough for you to validate them and (if needed) to round-trip them back to your page for editing or correction. If the controls validate, you can persist them to a database or other data store, where they will be available for subsequent GET requests.