Thursday, May 10, 2012

Getting PLL to build on my new machine - XSD Update Step

XSD Update

http://www.codesynthesis.com/products/xsd/

Get the latest, install, set an environment variable for the directory.  Do I need to plug in the binaries?
Restart Visual Studio to pick up the changed Environment Variable. Build.

Runtime version mismatch.... damit

Now it will not run the compiler......

Ok, got it to use the xsd.exe by putting it into the bin path correctly. But its failing with "The Handle is invalid"???? WTF? A File Handle? Is it open somewhere?

Tried picking apart the error by running the command line in a dos box.  It seems that Visual Studio is passing a bunch of flags to xsd.exe that have nothing to do with xsd.  Now Microsoft have their own XML compiler.... How do I turn that off?

So is it trying to treat it as an XML document or as XML Data?  Those seem to be the properties that are most likely. 

Ok, figured out how to set the custom build tool settings.  Right click on the file itself and go into the property pages. On the "General" set "Item Type" to Custom Build Tool.  Then its similar to the old custom build rules.

Now I find more info.... shit.
http://wiki.codesynthesis.com/Using_XSD_with_Microsoft_Visual_Studio

Ok, looking better.  Now I just need to figure out all the settings I used to have in my custom rule for xsd again... damit.

Ok. Plugged in the custom rule stuff.

There is now an enforced suffix on the generated parser skeleton files that was not there last time.  I can't figure out a way to turn it off.  So have to re-name all the files in TortoiseSVN.

Once thats all in place, the files are generating again, but they have different namespaces and type names, So I will need to check that there are no dependencies messed up.

No comments:

Post a Comment