I've written in the past about the Avalon schema that one gets installed with VS 2005 Extensions for WinFX.
Now that VS 2005 is final, I'm excited to take advantage of some bug fixes made in the Xml Editor to make the schema more useful.
Before I bother to go do that, I had sent mail out internally asking what our plan should be for installing the schema (should the Windows SDK distribute it also? if it did, where would it install it? etc...).
Somebody chimed in with the opinion that we shouldn't even ship the XSD because it currently gives both false positives and false negatives.
I'd love to hear opinions from our customers:
- if it is more trouble than help? should we stop shipping it?
- if we keep it alive, what we should focus on improving?
- what are the most common false positives (things that fail to compile, but things you don't get warned for)
- what are the most common false negatives (things that compile, but were warned for by the schema)
Thanks, Rob