1. The Skeleon .xml file pp 130 - 131 returns an error.... cute? :-)

    Could not find a part of the path 'C:\Programmer\Spil\World of Warcraft\Interface\AddOns\FrameXML\UI.xsd'

    wich must origin from the relative path-statement: ..\FrameXML\UI.xsd" ??

     

     

    The Skeleon .xml file pp 130 - 131 returns an error.... cute? :-)

    Could not find a part of the path 'C:\Programmer\Spil\World of Warcraft\Interface\AddOns\FrameXML\UI.xsd'

    wich must origin from the relative path-statement: ..\FrameXML\UI.xsd" ??

    The source was tested quite extensively, thanks.  Most of the errors that have come up are legitimate errors, or problems that cropped up in the production process.  What do you mean this "returns an error"?  As described quite extensively in the XML chapter there are two different things you can check in an XML document:

    • Is the document well-formed?  This can be checked by any number of utilities and checks that all start tags have end tags and the nesting of tags is proper.  There is nothing wrong with this example with regards to being well-formed.
    • Does the document validate against the schema?  This can't just be checked casually and requires you to specify the schema in the file itself, or as a separate argument to whatever validation system you are using.

    The Skeleton XML file is just fine.  You have to explain what "returns an error"means, since you have to be running some software on it to even get an error.  The relative path to the XML schema needs to be changed if the schema doesn't exist in that location.  Nothing we could have written would have worked for everyone, so we used the exact same schema declaration that all of Blizzard's code uses.

    In short, there's nothing wrong with the supplied code, so please come back and let us know what the actual issue is.