If I may make a suggestion, I think it would be better if you put Wisej-related settings in a separate Web.config configuration section and not the generally used appSettings. I prefer to keep my appSettings in a separate file and import it into the Web.config in a single line with
<appSettings configSource=”Config\appSettings.config” />
instead of messing with the Web.config every time I need to make a change. If I want to keep the same importing I will have to remove the generated appSettings section and copy/paste Wisej settings in my separate file.
Just a suggestion.
We only have two settings: default theme (optional) and the server license key. A wisej section still needs an entry to define the configuration reader class.
The handler and module setting have to be in the httpHandler, etc. Can those go in an external file?
Yes, in the generated project templates. What I had in mind was to have a specific config section in Web.config named “Wisej”, where all the Wisej-related settings would be stored, and where only Wisej would put key/value pairs (like the license). And leave the appSettings section for application settings only (like defining paths, switches, initialization parameters etc).