0

The only thing I could find so far were those two pages

Along with the respective "descriptions".

However, they are far from complete as is evidenced by the missing descriptions for elements underneath the Tool element.

So then I found the descriptions for VCProjectEngine in the VS installation folder:

C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.VCProjectEngine.xml

but it's unclear whether the names of the object properties is a 1:1 mapping to those inside the resulting .vcproj file?

Things appear to be a little more straightforward for newer VS versions (MSBuild based), but not completely.

0xC0000022L
  • 20,597
  • 9
  • 86
  • 152

1 Answers1

1

There are none that describe the whole project file. The thing is that many tags work by convention, many tasks can be declared and named inline by simply calling out to the task assembly.

So even though for the basic structure a XSD exists, there is none that describes every possible way a project file can be setup not can you validate the project file without loading the tasks and have them validate their own snippets.

jessehouwing
  • 106,458
  • 22
  • 256
  • 341
  • Thanks, that's of course disconcerting news, but alright. Which raises an interesting question for me, though. Shouldn't it be possible well-formed XML to always have a complete schema? – 0xC0000022L Jan 31 '14 at 13:16
  • Yes, but the valid schema would probably contain a lot of `xs:Any`'s in it, making it less than helpful. It's basically what is shipping with Visual Studio. Those parts that are well known have a schema, the parts where you can extend allow just about anything. – jessehouwing Jan 31 '14 at 13:22