"Christoph Schittko [MVP]" <INVALIDEMAIL@austin.rr.com> wrote in message
news:uG6Bp0U7EHA.2192@TK2MSFTNGP14.phx.gbl...
> Mike,
>
> The XML you posted deserializes fine with classes generated with the
> XSDObjectGen tool [0] I mentioned in my first post. I added a
> schemaLocation attribute to schema 0:
>
> <xs:import
> namespace="http://schemas.microsoft.com/SQLServer/reporting/reportdesign
> er" schemaLocation="schema1.xml" />
>
> for the tool to pick up the second schema when generating the classes.
>
> HTH,
> Christoph Schittko
> MVP XML
> http://weblogs.asp.net/cschittko
>
>
>
>
>
>
> [0] http://apps.gotdotnet.com/xmltools/xsdobjgen/
>
>> -----Original Message-----
>> From: Mike Sarbu [mailto:m_sarbu@yahoo.com]
>> Posted At: Monday, December 27, 2004 10:40 PM
>> Posted To: microsoft.public.dotnet.xml
>> Conversation: Deserialization issue
>> Subject: Re: Deserialization issue
>>
>> Well, I'm trying to deserialize an RDL file, generated by Visual
> Studio.
>> Please find the file attached.
>>
>> Thanks,
>> Mike
>>
>>
>> "Christoph Schittko [MVP]" <INVALIDEMAIL@austin.rr.com> wrote in
> message
>> news:uTHrQPJ7EHA.1452@TK2MSFTNGP11.phx.gbl...
>> > Can you post what XML files your dealing with? You said that they
> are
>> > generated by a Microsoft tool. Could you say which tool?
>> >
>> > HTH,
>> > Christoph Schittko
>> > MVP XML
>> > http://weblogs.asp.net/cschittko
>> >
>> >
>> >> -----Original Message-----
>> >> From: Mike Sarbu [mailto:m_sarbu@yahoo.com]
>> >> Posted At: Monday, December 27, 2004 9:46 PM
>> >> Posted To: microsoft.public.dotnet.xml
>> >> Conversation: Deserialization issue
>> >> Subject: Re: Deserialization issue
>> >>
>> >> Hi Dino,
>> >>
>> >> Thanks a lot for the pointers you gave me, they were great.
>> > Unfortunately,
>> >> I
>> >> still have problems.
>> >>
>> >> Sorry for the missing quotes in the example that I posted, I typed
> it
>> >> instead of doing a copy-paste. In the real file the quotes were
>> > present.
>> >>
>> >> Now about my issues:
>> >>
>> >> 1. The publisher (which is Microsoft) didn't publish the schema.
>> >> 2. xsd.exe cannot infer the schema from the xml file because of an
>> > error
>> >> in
>> >> the xml document: "The same table (somenamehere) cannot be the
> child
>> > table
>> >> in two nested relations". Now the xml file is generated by a
> Microsoft
>> >> tool,
>> >> so I would've expected it to be correct ...
>> >> 3. Even when I delete the offending elements, I can succesfully
>> > generate
>> >> the
>> >> schema, I then generate the class, which looks identical to the one
>> > you've
>> >> generated, but I get the same error when deserializing it.
>> >>
>> >> Thanks a lot for any other piece of advice that may help,
>> >>
>> >> Mike
>> >>
>> >> "Dino Chiesa [Microsoft]" <dinoch@online.microsoft.com> wrote in
>> > message
>> >> news:esdG5%23Q6EHA.2552@TK2MSFTNGP09.phx.gbl...
>> >> > Mike,
>> >> > to solve these sorts of problems, you can try working in the
>> > opposite
>> >> > direction. When I want to de-serialize a document of a
> particular
>> >> schema,
>> >> > here's what I do:
>> >> >
>> >> > 1. infer the schema from the document using xsd.exe (only
> necessary
>> > if
>> >> no
>> >> > schema is available. Really, the doc publisher should give you a
>> >> schema,
>> >> > you shouldn't have to infer it)
>> >> >
>> >> > 2. generate classes from that schema, using xsd.exe /c
>> >> >
>> >> > 3. build a test driver (20 lines of code) that instantiates the
>> > class
>> >> and
>> >> > then serializes it. Compare to the xml document you are trying
> to
>> >> match.
>> >> > You can then iterate on your schema or the generated class,
> tweaking
>> > it
>> >> to
>> >> > match what you want.
>> >> >
>> >> >
>> >> > -----
>> >> >
>> >> > In your case,
>> >> >
>> >> > A. the
>> >> > xmlns:someobj=http://www.abcinc.com/objectdefinition
>> >> > is not valid XML. Need quotes around this namespace value.
>> >> >
>> >> > B. you did not specify the rest of the XML doc, but the
> assignment
>> > of
>> >> the
>> >> > someobj prefix corresponding to the
>> >> http://www.abcinc.com/objectdefinition
>> >> > namespace seems to be unnecessary. This will not break your
>> >> > de-serialization, but it is superfluous.
>> >> >
>> >> > C. the class I got by following the steps above was this:
>> >> >
>> >> >
>> >>
>> >
> [System.Xml.Serialization.XmlTypeAttribute(Namespace="http://www.abcinc.
>> > co
>> >> m/objectdefinition")]
>> >> >
>> >>
>> >
> [System.Xml.Serialization.XmlRootAttribute(Namespace="http://www.abcinc.
>> > co
>> >> m/objectdefinition",
>> >> > IsNullable=false)]
>> >> > public class SomeObject {
>> >> > public string SomeField;
>> >> > }
>> >> >
>> >> >
>> >> > And it de-serialized your XML (with the necessary quotes added,
> and
>> > one
>> >> > element added for illustration) just fine.
>> >> >
>> >> > D. to produce a similar XML doc by serializing, use
>> >> > XmlSerializerNamespaces ns = new XmlSerializerNamespaces();
>> >> > ns.Add( "", "http://www.abcinc.com/objectdefinition" ); //
> this
>> > will
>> >> be
>> >> > the default (no prefix) namespace in the XML doc, eg,
> xmlns="..."
>> >> >
>> >> > before serializing, and be sure to specify this ns in the
>> > Serialize()
>> >> > step.
>> >> >
>> >> > s1.Serialize(xmlWriter, so, ns);
>> >> >
>> >> > -Dino
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > "Mike Sarbu" <m_sarbu@yahoo.com> wrote in message
>> >> > news:Omz4Eq95EHA.4028@TK2MSFTNGP15.phx.gbl...
>> >> >> Hello all,
>> >> >>
>> >> >> I have an XML file like this:
>> >> >>
>> >> >> <?xml version="1.0" encoding="utf-8"?>
>> >> >> <SomeObject xmlns="http://www.abcinc.com/objectdefinition"
>> >> >> xmlns:someobj=http://www.abcinc.com/objectdefinition>
>> >> >> .....
>> >> >> </SomeObject>
>> >> >>
>> >> >> And I want to deserialize it, so I created a class:
>> >> >>
>> >> >> [XmlRoot(Namespace="someobj", ElementName="SomeObject")]
>> >> >> class SomeObject
>> >> >> {
>> >> >> ....
>> >> >> }
>> >> >>
>> >> >> When calling the 'Deserialize' method of a serializer I get an
>> > error
>> >> >> "There's an error in the XML document (2,2)".
>> >> >>
>> >> >> If I don't use namespaces (which I cannot aford, since I get the
>> > file
>> >> >> from a
>> >> >> vendor), everything works fine:
>> >> >>
>> >> >> <?xml version="1.0" encoding="utf-8"?>
>> >> >> <SomeObject>
>> >> >> .....
>> >> >> </SomeObject>
>> >> >>
>> >> >> Deserialize without issues into:
>> >> >>
>> >> >> [XmlRoot]