We use dozens of third party modules and many of them require a change to the web.config to get them working properly. Many of the developers are making the change to the web.config during the initial setup process of the module and at this time a backup of the web.config is made. While this works excellent for the initial setup it is a nightmare when it comes time to upgrade IF those changes are not commented in the web.config.

We would like to make a simple request.

1st, if your module requires changes to the web.config please detail those changes in the documentation.

2nd, when the changes are made during setup, please add a comment regarding the changes in the web.config <--Changes Made By OurModuleName -->

This will allow users to identify those changes quickly when it comes time for an upgrade to the latest release of DNN and copy them over to the new web.config.

Thanks for listening!

I've gotten in the habit of backing up the web.config, installing the module or upgrade and running Beyond Compare to find the differences.  But a comment would help even more.

Jeff

Yes...  this is a bad thing IMO.      I just recently installed a new 4.8 install (and updated the out of date modules) and wanted to try out the new Reports module.

Well, reports module did use a bin\.dll but now uses app_code only.    
1.  it doesnt delete the dll
2.  it has to modify the web.config

Guess what something timed out, web.config was left corrupted, site wouldn't load, you can't see error because you can't read the error settings and default is RemoteOnly.

What a mess.