Sep 22, 2014 at 10:09 PM
Edited Sep 22, 2014 at 10:11 PM
After doing some work on a very large configuration management project at work, I've noticed some features that would be very useful for this tool in my own experience. Please feel free to discuss and share. Some of these may already be listed in other
discussions and/or Issues, but it would be nice to have a nice summary in this thread. Feel free to summarize your issue report here (with link to the issue) if it is not already included.
Custom Validator Class Support
Ability to incorporate custom validator classes into this tool instead of just using the CallBackValidator (which can be a little ugly). I'd like the tool to be able to find custom validator classes in my assemblies and make them available when adding new property
Support for Manual Config File Loading
This tool currently uses ConfigurationManager.GetSection when loading sections. I would like to have the option to support loading sections via a Configuration object when opened through something like "Configuration myConfig = ConfigurationManager.OpenMappedExeConfiguration(...".
In this case, the generated code would allow loading through this Configuration object. This would take more thought, because ConfigurationManager.GetSection is static, while the Configuration object (ex: myConfig ) is not. Also note: sections loaded this
way do not throw validation errors UNTIL properties are accessed.
Support ConfigurationSection Super Class
Be able to to have all sections inherit from your custom configuration section class (inherits from ConfigurationSection) instead of from ConfigurationSection. In our project, we have a ConfigurationSection super class that overrides the ConfigurationSection.PostDeserialize()