Re: [DOTNET] XMLSerialisation options...

2002-05-02 Thread Marsh, Drew
Brian Weeres [mailto:[EMAIL PROTECTED]] wrote: > I must be doing something wrong but I can't get rid of the > xmlns: Brian, Hey sorry, should have provided a sample. You need to Add an empty namespace to the XmlSerializerNamespaces object like so: XmlSerializerNamespaces namespaces = new XmlS

Re: [DOTNET] XMLSerialisation options...

2002-05-02 Thread Brian Weeres
a"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; ClassID="123"> Bob 1 What I really want is Bob 1 " string Thanks for any help. Brian -Original Message- From: Marsh, Drew [mailto:[EMAIL PROTECTED]] Sent: Wedn

Re: [DOTNET] XMLSerialisation options...

2002-05-01 Thread Marsh, Drew
Dean Cleaver [mailto:[EMAIL PROTECTED]] wrote: > 1. The classes you want serialised have to be public - but > this isn't really what I wanted for this project - I wanted > to hide the implementation from the "end user" of this > component - is there any way to avoid this? Sorry... that's just th

Re: [DOTNET] XMLSerialisation options...

2002-05-01 Thread Dean Cleaver
: [DOTNET] XMLSerialisation options... 1. your classes have to be public. There's no way around this. We've received a lot of feedback about this requirement, though, and are considering our options for future versions. 2. you can suppress these prefix definitions by passin

Re: [DOTNET] XMLSerialisation options...

2002-05-01 Thread Alex DeJarnatt
1. your classes have to be public. There's no way around this. We've received a lot of feedback about this requirement, though, and are considering our options for future versions. 2. you can suppress these prefix definitions by passing an empty XmlSerializerNamespaces class to the Serialize metho