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
- See stackoverflow.com/questions/366151/…Robert Harvey– Robert Harvey2009-08-16 22:55:59 +00:00Commented Aug 16, 2009 at 22:55
- @Robert it might be better to discuss the duplication issue if you disagree than to simply overwrite the edit.Rex M– Rex M2009-08-16 23:07:23 +00:00Commented Aug 16, 2009 at 23:07
- If you have substantial content to add, go ahead. Otherwise, I have already posted a comment about the duplication.Robert Harvey– Robert Harvey2009-08-16 23:08:26 +00:00Commented Aug 16, 2009 at 23:08
- @Robert duplicates are to be closed, not commented on. Please see the FAQ.Rex M– Rex M2009-08-16 23:09:07 +00:00Commented Aug 16, 2009 at 23:09
- The founders have made the purpose of editing clear on their blog. It's intended for substantial edits, not big traffic signs.Robert Harvey– Robert Harvey2009-08-16 23:10:23 +00:00Commented Aug 16, 2009 at 23:10
| Show 3 more comments
4 Answers
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.
Comments
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.
@Html.Serialize("Transfer", Model, SerializationMode.EncryptedAndSigned) And in controller add deserialized attribute.
public ActionResult Transfer(string id,[Deserialize(SerializationMode.EncryptedAndSigned)]Transfer transfer) 
2 Comments
Andrew Barber
ViewState in ASP.NET is not related to the Model of MVC. ViewState contains the state of controls; not the values of model objects.
Matt
This has been removed in MVC 5 Futures, but you can use MvcSerializer.Serialize instead. See stackoverflow.com/questions/25828553/…
Due to its basic design of maintaining the business layer separate from presentation layer, MVC Framework does not allow to preserve the State over HTTP,
However Cookies, Serializable classes,ViewData and ViewBag are good ways to preserve the state in MVC.
Comments
If you're wanting to make for example, a Wizard styled form, you could create a Serializable class to retain the viewstate:
[Serializable] public class MyWizard { public string Field1 { get; set; } public string Field2 { get; set; } } You could then serialize this class and use it in a similar way to using ViewState (as a hidden field in the form).
