maybe. in your example if class1 is serialiable, you are ok, else you will
fail.
if you mark a class Serializable, you are declaring the class can be
serialized. when serialization happens, each property is serialized using
reflection. if the datatype of the property supports serialization, you're
ok. if not, then serialization will fail.
if a class has a property whose datatype does not support ISerializable, or
some internal values need to be saved, then you need to implement
ISerializable.
for some classes there is no practical way to implement ISerializable, such
a DataReader, or a SQLConnection, or many classes that control unmanged
resources.
-- bruce (sqlwork.com)
> We are planning on using "SqlServer" mode for our ASP.NET session
> state.
[quoted text clipped - 60 lines]
>
> End Class
Evian Spring - 16 Feb 2006 01:43 GMT
Thanks it makes sense. When you "some internal values" for Class1 in
my example, you mean the private members of class1?