I think there is a way to stop this happening by altering the file produced by xsd.exe, but there are 2 other ways.
For this I have chosen to use a programmatical approach, which is as follows: This is easily achieved using some test code.
It can validate an XML document as it reads and parses the document.
In this example, we demonstrate how to activate such validation.
I don’t know about you lot but I work with XML files a bit, but I don’t have to mess around with XSD (xml schema) files that often.
And it seems like every time I do I forget what I did last time.
The illustration validates an XML document that the user chooses, either or catelog1against the XML Schema document
You need one schema and two XML files to validate against the schema.
Register the method Validation Error with the settings object's Validation Event Handler.
The Validation Error method is called if the document being read is found to be invalid or an error occurs (for example, the document cannot be found).
Apparently using LINQ to XML you have to have the schemas target Namespace match the namespace of the xml you are checking, because the validate method looks through the collection of schemas for one validating that documents namespace.