Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration schema validation using XSD and XML #1174

Closed
UgurAldanmaz opened this issue Jan 17, 2016 · 3 comments
Closed

Configuration schema validation using XSD and XML #1174

UgurAldanmaz opened this issue Jan 17, 2016 · 3 comments
Labels
enhancement Improvement on existing feature nlog-configuration wontfix

Comments

@UgurAldanmaz
Copy link
Contributor

Configuration should be validated before initialization process.

See #1121 and #1128

@304NotModified
Copy link
Member

Validation instead of Exception is a good idea, but not sure if we should do it by XSD.

The XSD isn't always up-to-date and it's difficult (I think) to unit test the whole config.

@s-sreenath
Copy link
Contributor

Then I would suggest we make this a standard to make sure we update the XSD when ever needed?

@snakefoot
Copy link
Contributor

snakefoot commented Aug 1, 2022

NLog 4.6 + NLog 5.0 have made the NLog-Configuration-Parser more strict (alerts on unexpected/misspelled properties). Think any improvements to configuration-file validation should be implemented in the NLog-Configuration-Parser. Since XSD validation is slow, and also requires XSD-file matches NLog-version.

Notice also XSD validation have been implemented with #3487

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement on existing feature nlog-configuration wontfix
Projects
None yet
Development

No branches or pull requests

4 participants