Be seen. Boost your question’s priority for more expert views and faster solutions
ViewState vs Session?
Kind of a novice question: if I create an instance of my own class and try to save it into the Session object, it works, but if I try to save it into my ViewState, then I get an error like "class x is not marked as serializable." For my edification, why is this?
Thanks very much...
Thanks very much...
Asked:
2 Solutions
Session is going to be more versatile. Though you can save other things into viewstate, it is generally used to preserve your control's state (ie: keep the same text in a box, same element in a dropdown selected) between postbacks.
Session State is somewhat unlimited in size (to a degree) but remember it uses memory on your serving machine, so overuse may be detrimental to performance -for this, keep in mind that each user has their own unique session; but this should only be a problem with a huge amount of users, or unusually large session variable storage.
Session State is somewhat unlimited in size (to a degree) but remember it uses memory on your serving machine, so overuse may be detrimental to performance -for this, keep in mind that each user has their own unique session; but this should only be a problem with a huge amount of users, or unusually large session variable storage.
On Serialization.
This has to do with how ViewState variables are passed betwixt server and client machines in byte format. Serialization is a process for saving data onto a file or memory buffer so a clone may be resurected latter, or (as in this case) so it may be transmitted across a network connection bytewise.
In ASP.Net, making a class Serializable is an extremely complicated task, involving adding the Serializable attribute to the class and... no, wait... that's it!
(Okay, there is a little more involved if you want to play around with advanced features, but the basics are all automated for you. Sweet!)
This has to do with how ViewState variables are passed betwixt server and client machines in byte format. Serialization is a process for saving data onto a file or memory buffer so a clone may be resurected latter, or (as in this case) so it may be transmitted across a network connection bytewise.
In ASP.Net, making a class Serializable is an extremely complicated task, involving adding the Serializable attribute to the class and... no, wait... that's it!
(Okay, there is a little more involved if you want to play around with advanced features, but the basics are all automated for you. Sweet!)
'VB Example
<Serializable()> Class Employee
// C# Example
[Serializable]
class Employee
if you want to save the class in ViewState, then
Add following attribute in class
[Serializable]
public class SomeWhat
{
}
or implement ISerializable interface in the class to be the class Serializable.
using System.Runtime.Serializabl
public class SomeWhat : ISerializable
{
}
then add this in to viewstate. okey.
Add following attribute in class
[Serializable]
public class SomeWhat
{
}
or implement ISerializable interface in the class to be the class Serializable.
using System.Runtime.Serializabl
public class SomeWhat : ISerializable
{
}
then add this in to viewstate. okey.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
Oh (sorry to piggy back), and do I have to be careful about how many objects I save to the session?