Adding Web.config schema validation to the Configuration Manager #4707
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #4706
Summary
Adding Web.config schema validation to the Configuration Manager. Other config files and non-XML files are ignored.
When user clicks on the
Save Changes
button, the file is sent to the server for validation. If the file is the Web.config file, the server validates its contents against the DotNetConfig.xsd schema, and returns a list of validation errors. Or an empty list if no errors are found.The browser then presents a summary of the validation errors in a popup window, and asks the user whether to continue the save operation or cancel.
I'm adding the DotNetConfig.xsd file as an embedded resource. Maybe in the future we can add more XSD files to validate other config files.
Also, I added a new unit tests project to cover this change.
Screenshots