I am building a module as a separate project (as explained in one of the dnn videos) and just referencing a bin folder of my web application listed as dnndev website on my local machine. I use module development template supplied by Chris Hammond. All works well, appart from the database stuff. I can make a new connection and use it from the module, but that is no good for the live site. I beleive I will need to know what is the default connection in the dnn web site, so I can use it. How do I get that during both, design time and runtime?
Alex

In addition to making use of the SqlHelper class from Microsoft.ApplicationBlocks.Data, you will still need to obtain the default database connection string from web.config. The DotNetNuke core API provides a handy method for doing just that:

Dim connectionString As String = DotNetNuke.Common.Utilities.Config.GetConnectionString()

If you are building a one-of-a-kind module for one of your own installations, that should be enough. However, if building a module that may be installed in a variety of sites, you will also need to handle cases where a databaseOwner token other than "dbo" and/or an objectQualifier token has been specified in the providers section of web.config. Take a look at the data provider implementation source code (usually in a class file named SqlDataProvider.vb) of any of the more recent core modules (available for download from their individual CodePlex project sites) to see how this is handled.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner