Posted 17 years ago
by Colin Blakey
-
Application Development Manager,
Vertex Inc
![Avatar](https://secure.gravatar.com/avatar/8d764e4214b40be33615615be59e3c3e.jpg?s=64&d=identicon&r=g)
I have two questions/comments which may or may not be considered bugs i.e it may just be the way the Microsoft XML code works.
1) When using a multi file schema (lots of includes) it is necessary to set the current directory to the schema location prior to loading the schema into the schema resolver otherwise you get schema loading errors.
2) With the above mentioned multi file schema, when passing to the editor control a part of the XML that has a schema for it (in our case an IRS1120 XML chunk has a matching IRS1120.XSD schema file) then I set the default namespace in the schema resolver to get the intellisense working but the schema validation does not work because I do not have a namespace element specified in the root node i.e. xmlns="http://www.irs.gov/efile" of the chunk because it's not there in the text.
Any help would be appreciated.
Thanks
Colin Blakey
1) When using a multi file schema (lots of includes) it is necessary to set the current directory to the schema location prior to loading the schema into the schema resolver otherwise you get schema loading errors.
2) With the above mentioned multi file schema, when passing to the editor control a part of the XML that has a schema for it (in our case an IRS1120 XML chunk has a matching IRS1120.XSD schema file) then I set the default namespace in the schema resolver to get the intellisense working but the schema validation does not work because I do not have a namespace element specified in the root node i.e. xmlns="http://www.irs.gov/efile" of the chunk because it's not there in the text.
Any help would be appreciated.
Thanks
Colin Blakey