I've had to change a class within an application.
The previous developer used serialization to store objects to file. He didnt
use ISerializable interface and even if he had.....
I just dont trust or like using serialization just for the reasons Im asking
for help about.
He used binary serialization, and Im getting errors when the file is read
from disk as the class has changed.
I need to be able to read files created with previous versions of this
software.

I added IDeserializable to try to diagnose the problem, but the deserialize
call fails at bfSkin.Deserialize and my callback to OnDeserialization is
never called.
Is there anything that i can do to step through the deserialization of my
object so that I could at least have a go at fixing it please?


FileStream fsSkin = new FileStream(sFileName, FileMode.Open);

BinaryFormatter bfSkin = new BinaryFormatter();

// Deserialize the object graph

rSkinFile=null;

try

{

rSkinFile = (SkinFile) bfSkin.Deserialize(fsSkin);

You only really need to implement ISerializable if you want to perform custom
serialization. Applying SerializableAttribute to your class is generally
enough for most people.

Check out Version Tolerant Serialization. You should get some good
resources with the following google search:
http://www.google.ca/search?hl=en&q=...lization&meta=

--
http://www.peterRitchie.com/


"Chukkalove" wrote:

> I've had to change a class within an application.
> The previous developer used serialization to store objects to file. He didnt
> use ISerializable interface and even if he had.....
> I just dont trust or like using serialization just for the reasons Im asking
> for help about.
> He used binary serialization, and Im getting errors when the file is read
> from disk as the class has changed.
> I need to be able to read files created with previous versions of this
> software.
>
> I added IDeserializable to try to diagnose the problem, but the deserialize
> call fails at bfSkin.Deserialize and my callback to OnDeserialization is
> never called.
> Is there anything that i can do to step through the deserialization of my
> object so that I could at least have a go at fixing it please?
>
>
> FileStream fsSkin = new FileStream(sFileName, FileMode.Open);
>
> BinaryFormatter bfSkin = new BinaryFormatter();
>
> // Deserialize the object graph
>
> rSkinFile=null;
>
> try
>
> {
>
> rSkinFile = (SkinFile) bfSkin.Deserialize(fsSkin);
>
>
>
>

Thanks for replying Peter
I'll never use serialization by choice. Was bitten before and there are
other ways to do a similar job.
My problem is that I need to be able to find some way to open and convert
files previously written with the serialization that's now broken because
its been very necessary to change the object.

thanks





"Peter Ritchie" <(E-Mail Removed)> wrote in message
news:F7014FB9-AFB2-47EA-80B1-(E-Mail Removed)...
> You only really need to implement ISerializable if you want to perform
> custom
> serialization. Applying SerializableAttribute to your class is generally
> enough for most people.
>
> Check out Version Tolerant Serialization. You should get some good
> resources with the following google search:
> http://www.google.ca/search?hl=en&q=...lization&meta=