Another nice idea! :-) Only problem is; if people upgrade, how do I keep it backwards compatible... Or should people read the release notes and notice this breaking change and they'll have to transfer their settings from the web.config to the dateFolders.config manually?
If user can be able to add config item to web.config, I think they can transfer their settings manually and easily.
I'm not a coder, I think if you tell me, the new version should remove three config items in web.config, and reset them in config/dateFolders.config just following example.
Just logged on here to suggest the same thing. I find it easier to keep track of what modules I've got installed if they have their own settings config. Seems to be the norm these days. Also lets me makes changes on the fly without have to restart my whole application pool (by touching web.config).
Another thing is when I'm installing a new plugin I like to expand the "Read more" box to see exactly what's gettings put into my solution; having a dedicated config files tells me that there are changes and modifications I can make. If all config options are set in the web.config then that's not immediately clear.
if possible, let all set item in a config file named dateFolders.config and saved it in config folder
I see config files of most modules are stored in config folder, I think this is better, and you can write example config in it as comment.
Another nice idea! :-) Only problem is; if people upgrade, how do I keep it backwards compatible... Or should people read the release notes and notice this breaking change and they'll have to transfer their settings from the web.config to the dateFolders.config manually?
If user can be able to add config item to web.config, I think they can transfer their settings manually and easily.
I'm not a coder, I think if you tell me, the new version should remove three config items in web.config, and reset them in config/dateFolders.config just following example.
I think I can do it easily.
Just logged on here to suggest the same thing. I find it easier to keep track of what modules I've got installed if they have their own settings config. Seems to be the norm these days. Also lets me makes changes on the fly without have to restart my whole application pool (by touching web.config).
Another thing is when I'm installing a new plugin I like to expand the "Read more" box to see exactly what's gettings put into my solution; having a dedicated config files tells me that there are changes and modifications I can make. If all config options are set in the web.config then that's not immediately clear.
is working on a reply...