Michael et al,

I have read this entire thead many times over and I think I am ready to install our own version of DNN.  We are currently using the value application version godaddy provides, but we need our own copy.  This post is quite long, but I want to make sure I understand everything I have to do before I try to install our own copy.  Below I have outlined the steps I will take, but I also have some questions. 
Could you kind souls please review my steps and questions, and help me out? 

My first step will be to create a DNN directory with all permissions marked and then create subdirectories with the permissions that Michael and others have indicated.  I do realize that my site will be at mysite.com/DNN and this is okay.  I will also create an SQL Server as per his instructions. 

Next, I will download the install version and unzip it into a folder named DNN on my hard drive.

Next, add my data to the connection strings: 

Question: Which connection string do I use?  The one with the SQL Server 2005 Express or the one without?  I do have VB Express as well as SQL Server 2005 Express.  Do I use the connection string with Server Express if I am doing the starter kit installation?    I would rather not if I don’t have to as I want to do my install from the Install version.  I also noticed it says kept for backwards compatibility with Legacy modules.  We do have a forum, so should I keep it for this purpose?   One other thing I noticed is that in string #2 the 2005 Server Express is commented out (I think I am using the correct terminology here – it has the <!—before and after it).  Doesn’t this mean it won’t be read? 

I will also make sure the string is all on one line with the three sections (name, connectionString, an providerName) separated only by spaces, and that I have my server, database name, user ID and password. 

Which do I use?  Connection string 1 or  

<connectionStrings>

<add name="SiteSqlServer" connectionString="Enter_Server_Urn;Database=Enter_Database_Name;uid=Enter_UserId;pwd=Enter_Password;" providerName="System.Data.SqlClient" />

</connectionStrings>

<appSettings>

<add key="SiteSqlServer" value="Server=Enter_Server_Urn;Database=Enter_Database_Name;uid=Enter_UserId;pwd=Enter_Password;" />

</appSettings>

Or Connection String 2?

<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=whsql-v06.prod.mesa1.secureserver.net;Database=DB_XXXXX;uid=xxxxxxx;pwd=xxxxxxx;" providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules -->
    <!-- <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/> -->
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules    -->
    <add key="SiteSqlServer" value="Server=whsql-v06.prod.mesa1.secureserver.net;Database=DB_XXXXX;uid=xxxxxxx;pwd=xxxxxxxx;"/>

At this point I would also change the custom errors mode to Off.  Should I also change the debug mode to true?  The debugging message always seems to come up on the text sites I have attempted to load. 

Next step is to move the SiteURL config to the root directory – which would be the DNN folder, correct?    

Last step should be to upload, via FileZilla, (unless someone can suggest a better FTP program) my DNN folder to my DNN directory that I created on godaddy, navigate to mysite.com/DNN on IE and cross my fingers! 

Does anyone see anything I missed? 

Thanks,

Michelle

This is incredibly dangerous and I highly recommend against it.  Creating your DNN site in a subdirectory is fine but don't just apply all permission because you completely void the security.  At most the subdirectory should have Read, Write and Web.  Do not give Browse permission. 

Actually, you use both connection strings.  Some of the older DNN Modules will require the connection string in the appSettings.  The 4.x site framework and newer modules will use the connection string from the connectionStrings section.

Please also take not that your connection string should all be on the same line, not both on the same line but the attributes for each connection string on the same line.  There is currently a problem with a line feed (return) in the connection string that causes an error.  This is an Asp.Net feature and not DNN.

You do not need to turn debugging on, this is done on a development machine only and will just cause your site to run slower.  It is also recommended that you do no turn customErrors mode to off.  This will create a vulnerability in your site.  The DNN framework has a robust error message feature, if you do get the Asp.Net errors you can then turn customErrors mode off while you fix the problem.

That is Correct.

That is a good practice and you have covered the process.

Setting up DNN in IIS is different from setting up DNN in a Shared Hosting environment, which is what my instructions and the other instructions in this thread are addressing.

In IIS you need to create a virtual directory first and apply the Asp.Net 2.0 Runtime to that directory, use the Asp.Net tab on the site configuration properties.  If your install directory is not within the wwwroot directory then you will need to give the Asp.Net User account permssions on the actualy directory.

Further configuration may be required depending on how your server is setup.