XML Deserialization

[yoshijg]

Is there a way to be notified when the deserialization of an XML is
complete, like a callback method?

I tried the IDeserializatio nCallback interface, but that doesnt for
XML-Deserialization .

thanks
josh

[Kevin Spencer]

Use a synchronous overload of the XmlSerializer.D eserialize method; when it
returns, it is finished.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.

"yoshijg" <jo*****@gmail. com> wrote in message
news:11******** **************@ g14g2000cwa.goo glegroups.com.. .

Is there a way to be notified when the deserialization of an XML is
complete, like a callback method?

I tried the IDeserializatio nCallback interface, but that doesnt for
XML-Deserialization .

thanks
josh

[yoshijg]

Hi Kev,

Do you mean something like this...

--
FooType fooobj;
XmlSerializer xmlObj = new System.Xml.XmlS erialialzer(Typ eOf(FooType));
Filestream strObj = new Filestream("foo ", Open);
fooobj = xmlObj.Deserial ize( strObj );
fooObj.Deserial izeComplete(); //Notify manually
--

Yeah, i am doing that now... but I want the object being created inside
of the "Deserializ e" method to be notified when it's done being created
by the "XmlSerializer" .

I can do what you suggest and it's easy...but some coder may forget to
call "DeserializeCom plete". Now I can wrap this whole thing in a
function call, but that's just another hoop everybody doesnt need to
jump through.

Now why doesn't implementing IDeserializatio nCallback work?

[Kevin Spencer]

I don't know why. How are you implementing it?

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.

"yoshijg" <jo*****@gmail. com> wrote in message
news:11******** **************@ g44g2000cwa.goo glegroups.com.. .

Hi Kev,

Do you mean something like this...

--
FooType fooobj;
XmlSerializer xmlObj = new System.Xml.XmlS erialialzer(Typ eOf(FooType));
Filestream strObj = new Filestream("foo ", Open);
fooobj = xmlObj.Deserial ize( strObj );
fooObj.Deserial izeComplete(); //Notify manually
--

Yeah, i am doing that now... but I want the object being created inside
of the "Deserializ e" method to be notified when it's done being created
by the "XmlSerializer" .

I can do what you suggest and it's easy...but some coder may forget to
call "DeserializeCom plete". Now I can wrap this whole thing in a
function call, but that's just another hoop everybody doesnt need to
jump through.

Now why doesn't implementing IDeserializatio nCallback work?

[yoshijg]

Hey kev,

Taking from the example above...

The only thing to add/note is that FooType implements the
IDeserializatio nCallback , and the call to deserialize looks like

FooType fooobj;
XmlSerializer xmlObj = new System.Xml.XmlS erialialzer(Typ eOf(FooType));
Filestream strObj = new Filestream("foo ", Open);
fooobj = xmlObj.Deserial ize( strObj );
---------------

Note, I am not calling OnDeserializati on manually like above.

[Kevin Spencer]

What I meant was, how are you implementing IDeserializatio nCallback? The
code you just posted doesn't do this. Your question was "why doesn't it
work?" In order to see why it doesn't work, I have to see how you're using
it.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.

"yoshijg" <jo*****@gmail. com> wrote in message
news:11******** **************@ g49g2000cwa.goo glegroups.com.. .

Hey kev,

Taking from the example above...

The only thing to add/note is that FooType implements the
IDeserializatio nCallback , and the call to deserialize looks like

FooType fooobj;
XmlSerializer xmlObj = new System.Xml.XmlS erialialzer(Typ eOf(FooType));
Filestream strObj = new Filestream("foo ", Open);
fooobj = xmlObj.Deserial ize( strObj );
---------------

Note, I am not calling OnDeserializati on manually like above.

[yoshijg]

/*
Serializes/Deserializes properly as expected. But doesnt call the
OnDeserializati on();
*/

using System;
using System.Xml.Seri alization;
using System.IO;
using System.Runtime. Serialization;

namespace Test
{
public class Class1
{
[STAThread]
static void Main(string[] args)
{
//Serialize to disk first
Foobar fooObj = new Foobar();
XmlSerializer xml = new XmlSerializer(t ypeof(Foobar));
StreamWriter ios = new StreamWriter("f oobar.xml");
xml.Serialize(i os, fooObj);
ios.Close();

//Deserialize from disk
Foobar fooObj2 = null;
XmlSerializer xml2 = new XmlSerializer(t ypeof(Foobar));
FileStream ios2 = new FileStream("foo bar.xml",
FileMode.Open);
fooObj2 = (Foobar)xml.Des erialize(ios2);
ios2.Close();

}
}

[Serializable()]
public class Foobar
: IDeserializatio nCallback
{
private string m_Foo = "fooooo";

public string FooProperty
{
get
{
return m_Foo;
}
set
{
m_Foo = value;
}
}

public void OnDeserializati on(Object sender)
{
Console.WriteLi ne("Deserializa tion complete");
}
}
}

[yoshijg]

/*
Serializes/Deserializes properly as expected. But doesnt call the
OnDeserializati on();
*/

using System;
using System.Xml.Seri alization;
using System.IO;
using System.Runtime. Serialization;

namespace Test
{
public class Class1
{
[STAThread]
static void Main(string[] args)
{
//Serialize to disk first
Foobar fooObj = new Foobar();
XmlSerializer xml = new XmlSerializer(t ypeof(Foobar));
StreamWriter ios = new StreamWriter("f oobar.xml");
xml.Serialize(i os, fooObj);
ios.Close();

//Deserialize from disk
Foobar fooObj2 = null;
XmlSerializer xml2 = new XmlSerializer(t ypeof(Foobar));
FileStream ios2 = new FileStream("foo bar.xml",
FileMode.Open);
fooObj2 = (Foobar)xml.Des erialize(ios2);
ios2.Close();

}
}

[Serializable()]
public class Foobar
: IDeserializatio nCallback
{
private string m_Foo = "fooooo";

public string FooProperty
{
get
{
return m_Foo;
}
set
{
m_Foo = value;
}
}

public void OnDeserializati on(Object sender)
{
Console.WriteLi ne("Deserializa tion complete");
}
}
}

[Kevin Spencer]

Well, you havent implemented the interface. See the following MSDN article:

http://msdn.microsoft.com/library/de...ationTopic.asp

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.

"yoshijg" <jo*****@gmail. com> wrote in message
news:11******** **************@ g49g2000cwa.goo glegroups.com.. .

/*
Serializes/Deserializes properly as expected. But doesnt call the
OnDeserializati on();
*/

using System;
using System.Xml.Seri alization;
using System.IO;
using System.Runtime. Serialization;

namespace Test
{
public class Class1
{
[STAThread]
static void Main(string[] args)
{
//Serialize to disk first
Foobar fooObj = new Foobar();
XmlSerializer xml = new XmlSerializer(t ypeof(Foobar));
StreamWriter ios = new StreamWriter("f oobar.xml");
xml.Serialize(i os, fooObj);
ios.Close();

//Deserialize from disk
Foobar fooObj2 = null;
XmlSerializer xml2 = new XmlSerializer(t ypeof(Foobar));
FileStream ios2 = new FileStream("foo bar.xml",
FileMode.Open);
fooObj2 = (Foobar)xml.Des erialize(ios2);
ios2.Close();

}
}

[Serializable()]
public class Foobar
: IDeserializatio nCallback
{
private string m_Foo = "fooooo";

public string FooProperty
{
get
{
return m_Foo;
}
set
{
m_Foo = value;
}
}

public void OnDeserializati on(Object sender)
{
Console.WriteLi ne("Deserializa tion complete");
}
}
}

[yoshijg]

Hey Kev,

Thanks for the article. I guess IDeserializatio nCallback only works
with the "BinaryFormatte r", which really seems counter intuitive.
Don't you? Wouldn't you expect a Callback to occur for any type of
Deserialization .
josh