Why can't an XmlDocument be passed via remoting?

[William]

I don't get it? Of all things, shouldn't an XmlDocument type be serializable
by default? How can I pass this type through a remoting service?

It just doesn't make sense, especially since DataSets can be passed, which
are XML.

[Nicholas Paldino [.NET/C# MVP]]

William,

I would have thought the same thing. However, it's easy to work around.
Just return a string.

I know it's not optimal, but it will work.

You could always load the XmlDocument into a DataSet and then return
that if you want to expose an object.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"William" <nf*@nospam.com> wrote in message
news:Oh**************@TK2MSFTNGP04.phx.gbl...

I don't get it? Of all things, shouldn't an XmlDocument type be
serializable
by default? How can I pass this type through a remoting service?

It just doesn't make sense, especially since DataSets can be passed, which
are XML.

[Tom Porterfield]

William wrote:

I don't get it? Of all things, shouldn't an XmlDocument type be
serializable by default? How can I pass this type through a remoting
service?
It just doesn't make sense, especially since DataSets can be passed, which
are XML.

Don't know, but it is trivial to take an XmlDocument to a string, which can
be passed via remoting.
--
Tom Porterfield

[chanmm]

You can put you XML into dataset and pass it like this:

private DataSet GetUserData()

{

// Set the path of the XML file and XML schema.

string strPath = Server.MapPath(".");

// Declare a data set.

DataSet dsUsers = new DataSet();

// Apply the XML schema to data set.

dsUsers.ReadXmlSchema(strPath + "\\UserInfo.xsd");

// Read the XML into the data set.

dsUsers.ReadXml(strPath + "\\UserInfo.xml");

return dsUsers;

}

chanmm
"William" <nf*@nospam.com> wrote in message
news:Oh**************@TK2MSFTNGP04.phx.gbl...

I don't get it? Of all things, shouldn't an XmlDocument type be
serializable
by default? How can I pass this type through a remoting service?

It just doesn't make sense, especially since DataSets can be passed, which
are XML.

[William]

Thank you.

Actually, what I wound up doing is something like this:

[WebMethod]
public XmlDocument Order(XmlDocument doc)
{
IOrder rObj = (IOrder)Activator.GetObject(typeof(IOrderCert),
ConfigurationManager.AppSettings["PocRemotingServer"]);
string ret = rObj.Order(doc.InnerXml);
XmlDocument retxml = new XmlDocument();
retxml.InnerXml = ret;
return retxml;
}

On the remote server side, I rebuild the XmlDocument and consume it in the
Business Logic Layer, which expects and XmlDocuement.

All a bit hokey and I am at a loss to explain why Microsoft decided to make
such an obvious task a bit of a hassle.

"chanmm" <ch*****@hotmail.com> wrote in message
news:eM**************@TK2MSFTNGP02.phx.gbl...

You can put you XML into dataset and pass it like this:

private DataSet GetUserData()

{

// Set the path of the XML file and XML schema.

string strPath = Server.MapPath(".");

// Declare a data set.

DataSet dsUsers = new DataSet();

// Apply the XML schema to data set.

dsUsers.ReadXmlSchema(strPath + "\\UserInfo.xsd");

// Read the XML into the data set.

dsUsers.ReadXml(strPath + "\\UserInfo.xml");

return dsUsers;

}

chanmm
"William" <nf*@nospam.com> wrote in message
news:Oh**************@TK2MSFTNGP04.phx.gbl...

I don't get it? Of all things, shouldn't an XmlDocument type be
serializable
by default? How can I pass this type through a remoting service?

It just doesn't make sense, especially since DataSets can be passed,
which are XML.