Visual studio 2016 validating xml schema

We can definitely explore into adding this feature.

The scope for this first version of the language server was set to XML.

I've noticed that your extension doesn't validate or provide intellisense for XSLT/XSL or XSD files automatically. Second, although the xsl namespaced elements seem to get validation and intellisense, other xml namespaced elements fail validation, even with an explicit schema declaration.

I've therefore used the file association facility with the following settings, using the schemas supplied with Visual Studio Mac. Finally, I get a schema file error with the file, so can't validate XSD documents.

Here is an example of how the association would look like: “xml Associations”: [ ] You can find a working version of the sample above in the file that is included in the readme.

Establishing the file association this way makes it far more convenient than having to manually invoke validation from the command window.

I would like to exclude the xml linting part to either the xml tools extension (who I did not contact so far, but will do now) or a standalone extension, but for that it should have a minimum standard. This extension, on the other hand, can handle any schema you throw at it, including complex structures like nested imports and includes.

I agree that being able to run validation against a schema from within the document being edited is convenient, especially if the option to establish the association at that time is provided.Been looking for an excuse to try at a vscode extension and Typescript 2.1 Hi there, I am currently working on an extension for ui5, which also heavily depends on xml files.I started to integrate a simple xml language server.With regards of your question, we do support direct selection of an XSD file to validate against an XML document through a feature called “File association”.You simply have to add an entry in .vscode/with the file name (or pattern) and the system Id, which would be the path to the XSD file, or optionally an entry in the XML Catalog (if you happen to be using one).

Leave a Reply