|
|
|
|
|
|
|
|
Thursday, September 09, 2010
|
|
|
|
|
|
|
|
|
|
|
|
|
Upgrading to DotNetNuke Cambrian 5.0 from DotNeNuke 4.x If you're looking to try out the new DNN Cambrian package, you can upgrade previous DotNetNuke installations with the following steps. Remember, as of right now, the DNN 5.0 Cambrian package availabl...
Find this article and more in the category
Read This Article . . .
Adding Google AdSense with Video Adding Google AdSense to your DotNetNuke portal has never been easier. By default, a Google AdSense module is added the list of installed modules when your DNN portal is first created. It's easy to ...
Find this article and more in the Modules category
Read This Article . . .
How to Install and Configure ActiveDirectory Provider for DotNetNuke 5.0 The directions for installing and configuring extensions in DotNetNuke 5.0 are very similiar, but slightly different than from previous versions. Here's how to install the ActiveDirectory authentica...
Find this article and more in the category
Read This Article . . .
Setting Up the DotNetNuke Side of Multi-Websites Ok, so by now you know that DotNetNuke can handle multiple websites, but you still want to know why. Well, it’s pretty easy once you know how to do it, but it can be pretty confusing to some who are ...
Find this article and more in the category
Read This Article . . .
Installation from the DotNetNuke Install Package 4.90 to Windows XP Professional OK, so you made the leap and downloaded an installation package of DotNetNuke 4.x. But now what do I do? Well, here's a step-by-step instruction guide to get you up and running with DotNetNuke 4....
Find this article and more in the Localhost category
Read This Article . . .
New DotNetNuke 5.0 Cambrian Package Writer for Module Developers Attention developers! DotNetNuke 5.0 Cambrian has a nifty new tool to help developers package their modules nicely to fit with the new “Extensions” manager. Under the old Module Definitions manager, ...
Find this article and more in the category
Read This Article . . .
Getting Aquainted with the DNN Classes So, you've decided to start checking out DotNetNuke development and you're wondering where to start, right? Well, it's easy to start taking a quick tour of the DotNetNuke classes now with the help o...
Find this article and more in the category
Read This Article . . .
Resolving Troubles with DNN User Controls During Module Development & Compilation So, you've created a module in a separate project using some DNN User Controls and now you're receiving errors and can't compile?
If you are using these controls (list below) on your module using ...
Find this article and more in the category
Read This Article . . .
Generate a Module Data Access Layer With CodeSmith With the introduction of some of the newer DNN tools, building a custom module is becoming more and more easy. With the right tools, you can have a custom module built in no time flat. This will outl...
Find this article and more in the DotNetNuke category
Read This Article . . .
I Need to Modify the What to Install DNN? What in the World is a Web.Config File Anyway?? If you're wondering what in the world a web.config file is, then wonder know more. . .in about 5 minutes, you'll know more than you do now and be well on your way to moving forward.
Find this article and more in the Web.Config category
Read This Article . . .
|
|
|
|
|
|
|
|
|
Article List
|
SERIES: Anatomy of a DNN Web.Config File-connectionStrings
|
| 12/9/2008 3:30:22 PM - By Briana Tarrance |
Category: | | Comments 0
|
| |
|
The <connectionStrings> section holds all the necessary information for database communication from your website. At minimum, there will be at least one connection string for any DotNetNuke website.
By default, the config files that come with your DotNetNuke website has two connection string elements in them; although one is commented out (shown in green below). It is there mainly to give you the proper syntax for creating a connection to a database that is physically located outside of your websites structure. The uncommented connection string is the proper syntax for a connection made to a SQL Express database that is physically located in the App_Data folder within your website structure.
<connectionStrings>
<!-- Connection String for SQL Server 2005 Express -->
<add name="SiteSqlServer"
connectionString="Data Source=.\SQLExpress;
Integrated Security=True;
User Instance=True;
AttachDBFilename=|DataDirectory|Database.mdf;"
providerName="System.Data.SqlClient" />
<!-- Connection String for SQL Server 2000/2005
<add name="SiteSqlServer"
connectionString="Server=(local);
Database=DotNetNuke;
uid=;pwd=;"
providerName="System.Data.SqlClient" />
-->
</connectionStrings>
As you can see from above, the “name” of the element is “SiteSqlServer”. While you technically can change this name, it is tightly coupled with DotNetNuke and changing the name may have adverse affects with DotNetNuke operations or third party modules. This connection string will dictate where your DotNetNuke data will be stored and retrieved from. Once you have your proper connection string set, there is no need to keep both of these strings on your config file. Some people choose to get rid of the extra lines for simplification and others prefer to leave it for future reference or “just in case”. Either way will work fine.
For more information on connection strings or for proper syntax with other types of database servers, visit http://www.connectionstrings.com/
|
| |
Related Articles
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|