1. Does anyone have any experience using XML Nanny for Verifying AddOn XML.  I keep getting warnings that it cannot read files along with a significant number of errors for elements that shouldn't be generating them.  If someone could point out where I might be going wrong I would be appreciative.

    Thanks

    -z

  2. Does anyone have any experience using XML Nanny for Verifying AddOn XML.  I keep getting warnings that it cannot read files along with a significant number of errors for elements that shouldn't be generating them.  If someone could point out where I might be going wrong I would be appreciative.

    Thanks

    -z

  3. I use it every single time I write an XML file.  Change the <Ui> element as follows:

    <Ui xmlns="http://www.blizzard.com/wow/ui/"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xsi:schemaLocation="http://www.blizzard.com/wow/ui/

    http://wowprogramming.com/FrameXML/UI.xsd">

    </Ui>

    I explain this a bit more in the new edition.  The xmlns attribute just defines the namespace we're using, in case there are multiple schemas being defined.  The xmlns:xsi then tells the validator what schema instance document we're using (i.e. what standard set the schema belongs to).  Finally the xsi:schemalocation attribute is a pair of strings, matching the namespace with where the document can be located.

    If you change the second half of that pair from ..\UI.xsd or ..\FrameXML\UI.xsd or whatever it is to the version of the schema we host here (http://wowprogramming.com/FrameXML/UI.xsd) then it will download that file and validate against it.  I find this incredibly convenient and useful.

    Please let me know if you have any other questions!

  4. Thank you for your quick reply.  I will try this out on my next pass with the XML file.