Some very interesting reading on IPC/Remoting here:
http://blogs.msdn.com/jackg/archive/2007/03/05/net-remoting-appdomains-out-of-process-two-way-etc.aspx
--
"I am Dyslexic of Borg. Resistors are fertile. Prepare to have your
ass laminated." -- Dan Nitschke
Marc C. Brooks
http://musingmarc.blog
Yes, it is possible. For example,
YourType obj = new YourType();
XmlSerializer serializer = new XmlSerializer( typeof( YourType ) );
XmlSerializerNamespaces namespaces = new XmlSerializerNamespaces( );
namespaces.Add( "", "" );
XmlWriterSettings settings = new XmlWriterSetting
Is it possible to create an XmlSerializer that will not create the xmlns
attributes and add the encoding type to the resultant xml serialized
document?
Here's what's created:
http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="
http://www.w3.org/2001/XMLSchema"; id="afac03d2-2a9c-42d0-a93c
Sadly my final outcome was to use the GAC for about 6 components. Another
complication I had to overcome was the remoting configuration - I use a
customised compression sink based on Ingo Rammer's sample, but I cannot figure
out how to configure that in code - so I have to ship a .config file, a
Out of curiosity, any follow-up on this ? I might run into this same
kind of issues soon...
Sébastien
On 2/28/07, Dean Cleaver <[EMAIL PROTECTED]> wrote:
Hi,
My issues aren't with the returned serialisable classes - it's with the
remote classes. Strangely, I can create an instance of my remote
