Validating against xsd schema
I am using this simple snippet, always works and you don't need complicated functions. PSObject Add-Member -Input Object $Context -Member Type Note Property -Name Configuration -Value "" $Configuration Path = $(Join-Path -Path $PWD -Child Path "Configuration") # Load xml and its schema $Context. Add($null, $(Join-Path -Path $Configuration Path -Child Path "Configuration.xsd")) | Out-Null # Validate xml against schema $Context. Validate( ) the solution of (Flatliner DOA) is working good on PSv2, but not on Server 2012 PSv3.It this example I am loading configuration xml with data which are used later for deployment and server configuration: # You probably don't need this, it's just my way $script: Context = New-Object -Type Name System. Configuration = [xml](Get-Content -Literal Path $(Join-Path -Path $Configuration Path -Child Path "Configuration.xml")) $Context. the solution of (wangzq) is working on PS2 and PS3!!
How do I set the Visual IDE up to notify me of validation failures, and then provide an intellisense list of valid tags and attributes in a given context?
This might depends on the library you use but googling around with "how to validate xml file in java" gave me these results where you might find your answer: first interesting result second interesting result Validator v = Language(Languages.
Validating an XML File against a XSD Schema This section describes different ways to validate XML files against XSD schemas: using standalone XML validation tools, using on-line XML validators, and writing your own XML validation programs.
The XML plugin is installed properly in the plugins subdir and the 3 DLLs are copied to the Notepad EXE subdirectory.
Other XML "validation" features work but there is no way to validate against an XSD. EDIT: Plugin manager was not included in some versions of Notepad because many users didn't like commercials that it used to show.
Turns out the file I was trying to validate didn't have an 'xml' file extension.