For me, when I say "serialize" I mean to convert an object into a different
format for easy storage or transmission.
For example, say you have an Employee object with properties like Name, Age,
Salary, etc. You programmatically create an instance of that object and set
its values. Now, what if you wanted to store that object on your hard drive
when the user closes your application?
To do that, you would have to write some code to write the values to a text
file, XML file, database, something. That processing of converting your
object to a file or whatever would be "serializing" your object.
When someone starts your application up again, you might need a way to load
that object back up from the XML file, etc. The process of getting the
information from the file, creating a new Employe object, setting the
values, etc. would be "deserializing" it.
Others here may have a better way of explaining it. :)
--
Ben Strackany
www.developmentnow.com
"Rachel Suddeth" <ra****@bldhound.com> wrote in message
news:u$**************@TK2MSFTNGP10.phx.gbl...
? I have seen apparently different meanings... If you say "designer
serialization", it seems to mean that a setting is put into
"InitializeComponent" by the designer. Then remoting stuff talks about
serialization that has a different meaning that I can't seem to
understand. None of the articles I've looked at explain what it means -- they seem to
feel it's something standard. I've done network programming, but not with
Windows (or even PC's, really) so maybe I've missed because of that.
Anyway, I think there must be something the two meanings have in common?
Thanks,
Rachel
__________________________________________________ ____________
Roydan Enterprises Ltd
602 North 9th Street
Manitowoc, WI 54220-3924