Re: Problem with xsd.exe
- From: "Mr. Arnold" <MR. Arnold@xxxxxxxxxx>
- Date: Thu, 20 Dec 2007 23:51:48 -0500
"Schemer" <nowhere@xxxxxxx> wrote in message news:OM92v4nQIHA.1212@xxxxxxxxxxxxxxxxxxxxxxx
>xsd.exe /?
Microsoft (R) Xml Schemas/DataTypes support utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved
When I try this command:
xsd /c /e:Transaction /l:cpp LargeSchema.xsd
I get a number of "schema validation: warnings and "element is not declared" warnings. Finally, processing stops with a "datatype xxx is missing" error.
LargeSchema.xsd opens and validates in XMLSpy. Is it possible the schema is too complex for xsd.exe to handle? Are there any alternatives to xsd.exe?
Thanks for any suggestions.
Most likely, there is another schema involved, and include schema, that has to be accounted for in the build.
If the XSD is valid, then you should be able to pull all schemas involved into a project by using VS Project Add Existing Item, which will resolve or expose all problems with the XML schema.
The one area that you can look it is the <namespace> tag, which indicates what namespace the XML is in and is using.
XML.xsd that is not in the same <namespace> as the parent XSD can cause a missing element condition, along with the <include> XSD not being found period.
.
- Follow-Ups:
- Re: Problem with xsd.exe
- From: Schemer
- Re: Problem with xsd.exe
- References:
- Problem with xsd.exe
- From: Schemer
- Problem with xsd.exe
- Prev by Date: Problem with xsd.exe
- Next by Date: Re: Problem with xsd.exe
- Previous by thread: Problem with xsd.exe
- Next by thread: Re: Problem with xsd.exe
- Index(es):
Relevant Pages
|