Play the VDF15.1 RC1 Quiz
byon 4-Dec-2009 at 02:17 PM (1336 Views)
I'd like to talk about two of the changes made in our Visual DataFlex 15.1 Release Candidate (VDF15.1 RC1). We wrote a new help section about XML namespaces (Reference Library / General Reference / XML Namespaces Primer). That's the good change. We accidentally copied the wrong XML file into our new workspace template section. That's the evil change. Now when you try to create a new workspace you get the following error:
The error is reported here and the fix for it is found here.
Coincidentally the cause of this error can be explained by information provided in the XML Namespaces Primer. It seemed like this might be a good chance to test our new documentation. Can you tell us why the Studio reported this error?
Here is some extra information. The Studio raised this error when it tried to open and read our "empty" DDClassList.xml file. The file is a properly constructed XML file but the Studio immediately recognized that the file was wrong. Here's the bad file:
The file that would have worked looks like this:Code:<DataDictionaryList xmlns="http://www.dataaccess.com/VisualDataFlex/2008/DataDictionaryList/"> <DDClasses/> </DataDictionaryList>
In addition, this file would have worked as well:Code:<DataDictionaryList xmlns="http://www.dataaccess.com/VisualDataFlex/2006/DataDictionaryList/"> <DDClasses/> </DataDictionaryList>
Here's another clue. We changed the format of the DDClassList.xml file in VDF14.1. If the Studio encounters an old format file it automatically converts it to the newer format. In this case, it didn't even try.Code:<DataDictionaryList xmlns="http://www.dataaccess.com/VisualDataFlex/2008/DataDictionaryList/"> <Tables/> </DataDictionaryList>
And one last clue. Every single node in this bad XML file is wrong!
The question to you is, why did the Studio decide that the XML file in RC1 is invalid? The answer is in the XML Namespaces primer. You will have to download and install RC1 to read this primer.
You get extra credit if you can write the code that would recognize that the file is invalid.
(Perhaps we even added this bug to RC1 to get you all to read the new help section. Could we possibly be that clever?)