Click here to Skip to main content
15,867,704 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Why do we need to serialize Viewstate only. Why not any other State Management Technique??
Posted

Well, by default the other states (Application, Session, Cache) are managed "In Process", that is, within the same .NET process. If you want to use a "Out of process" implementation for those states, you need to serialize/de-serialize objects obviously.

For example, if you manage the Session in a State server, the Asp.net runtime will need to serialize/de-serialize the objects for storing/retrieving objects to/from the state server. Also, if you use any distributed caching engine, objects are required to be serialized/de-serialized.
 
Share this answer
 
As Subho said, Its not only the view state that you need to serialize. You also need to serialize in other techniques as well, but it is required only when you save these data in outproc mode ie sqlserver, state server or some custom, based on technique.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month


CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900