I have some custom modules that talk to an MSSQL database, seperate to DNN's own database.

In itself, doing this is straightforward enough as I will be targetting MSSQL only, so my modules talk directly to their data using SQL Client, ADO.NET, conenction strings, and so on.

Of course that raises the problem of multiple connection strings in multiple custom modules, which need to be changed depending on whether the modules are on my dev system or a production server.

In vanilla ASP.NET or whatever you would just use a config file with a parameter and change it once in there, however I don't see a simple way of that working under DNN.

What do you other DNN l33t haXXors do !!??

Another item you could consider is making the connection string a module setting....but that would require configuration on each module instance, however it would NOT require modification of a web.config file.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services