Hi everyone!

This looks a good place for asking my question here.

Let starts from the problem and then I will give you some brief about the module which might help you to understand the problem in a big picture. The problem is, the dotnetnuke module is depended on two different configurations that we putted on the web.config file. Everytime when there are priority updates requested from Dotnetnuke community the deployment need to be very careful with web.config migration. The configuration about another database configuration settings and a webservice configuration & settings. The module required to request the data different from dotnetnuke database and a webservice.

 What would you suggest what should we do to ease our deployment procedure and a better way to manage module configuration?

Thanks for your time! I will be looking forward for a solution that do good and required least :-)

Thanks!

It sounds like you are running into a common ASP.NET problem that is not only as issue for DNN but for any app that uses connection strings.  If you have several developers that all use there own database managing the web.config file is very difficult.  In ASP.NET 1.1 we used the very cool user.config file that we did NOT put in source control but if it was present in the developer's working folder that would take precidence over the web.config file.  Unfortunatly that only works for the appSettings group so this does not work for the ConnectionString group in ASP.NET 2.0.  Unfortunatly I don't have any suggestions for you other than we are feeling your pain as well.  Maybe MS gave us some other options in 3.5, I havn't checked yet.