Hi,

Sorry for the late article. I did'nt know how to add screenshots to the article.

In case of installing with SQL Express 2005 we need to create the SQLExpress database which isn’t provided with the DNN 4.0 installer. This time we’ll use the source in DotNetNuke_4.0.0_Source.zip. Here’s how you can get it to work.

 

Instructions :-

 

1.                  Unzip the contents of the zip file DotNetNuke_4.0.0_Source.zip to a physical directory on the file system, say c:/dotnetnuke. This will result as two directories Website, Library and a file DotNetNuke.sln.

 

 

2.                  Right-click the folder c:/dotnetnuke and click Properties, in the dialog that show up select the Security tab and add a user named NETWORK SERVICE and assign it full access to the folder.

 

 

3.                  Open the DotNetNuke.sln file with Microsoft Visual Studio 2005. If the VS.NET 2005 prompts the message below, click Yes.

 

 

4.                  Open the file Mail.vb under the folder Mail in the project DotNetNuke.Library and comment out the line 138 as shown below.

 

 

5.                  Try to build the solution.

 

 

6.                  Most probably you’ll get 45 Errors as shown below..... I got them.

 

 

7.                  To remove these errors if you get them, is easy. Open the ClientAPI.vb file under the project DotNetNuke.WebUtility as shown below and Build the solution once again (OK i know, i know... no time for the details just do it). The build will succeed.

 

 

8.                  Rename the file release.config under the http://localhost/DotNetNuke_2/ project to web.config as shown below.

 

 

9.                  Now right-click on the App_Data folder under the http://localhost/DotNetNuke_2/ project, click Add New Item.

 

 

10.              On the dialog that appears select SQL Database. Let the default name be Database.mdf and click Add.

 

 

11.              This will add an SQLExpress db named Database.mdf under the App_Code folder.

 

 

12.              Now open the browser and browse the following url http://localhost/Dotnetnuke_2 . You’ll end up with the error shown below. The reason is that currently you’re running .NET Framework Beta whereas the DNN 4.0 requires .NET Framework 2.0 RTM version. Download the framework from http://www.microsoft.com/downloads/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5&DisplayLang=en and install it. You might need to uninstall the Beta framework.

 

13.              After you install the .NET Framework 2.0 you need to configure the virtual directory with Asp.NET 2.0. To do this, open IIS Manager right-click the virtual directory DotNetNuke_2 under the Default Web Site, and select Properties. A dialog appears, select ASP.NET tab and specify the ASP.NET version as 2.0.50727. Click Apply and OK.

 

 

14.              Now refresh/browse the url http://localhost/Dotnetnuke_2

 

Hope that helps.

Useful post muhafad, it would help to edit the images and make them smaller.

Updated the broken images issue.

In case of installing with SQL Express 2005 we need to create the SQLExpress database which isn’t provided with the DNN 4.0 installer. This time we’ll use the source in DotNetNuke_4.0.0_Source.zip. Here’s how you can get it to work. 

Instructions :-

1.                  Unzip the contents of the zip file DotNetNuke_4.0.0_Source.zip to a physical directory on the file system, say c:/dotnetnuke. This will result as two directories Website, Library and a file DotNetNuke.sln.

 

2.                  Right-click the folder c:/dotnetnuke and click Properties, in the dialog that show up select the Security tab and add a user named NETWORK SERVICE and assign it full access to the folder.

 

 

3.                  Open the DotNetNuke.sln file with Microsoft Visual Studio 2005. If the VS.NET 2005 prompts the message below, click Yes.

 

 

4.                  Open the file Mail.vb under the folder Mail in the project DotNetNuke.Library and comment out the line 138 as shown below.

 

 

5.                  Try to build the solution.

 

 

6.                  Most probably you’ll get 45 Errors as shown below..... I got them.

 

 

7.                  To remove these errors if you get them, is easy. Open the ClientAPI.vb file under the project DotNetNuke.WebUtility as shown below and Build the solution once again (OK i know, i know... no time for the details just do it). The build will succeed.

 

 

8.                  Rename the file release.config under the http://localhost/DotNetNuke_2/ project to web.config as shown below.

 

 

9.                  Now right-click on the App_Data folder under the http://localhost/DotNetNuke_2/ project, click Add New Item.

 

 

10.              On the dialog that appears select SQL Database. Let the default name be Database.mdf and click Add.

 

 

11.              This will add an SQLExpress db named Database.mdf under the App_Code folder.

 

 

12.              Now open the browser and browse the following url http://localhost/Dotnetnuke_2 . You’ll end up with the error shown below. The reason is that currently you’re running .NET Framework Beta whereas the DNN 4.0 requires .NET Framework 2.0 RTM version. Download the framework from http://www.microsoft.com/downloads/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5&DisplayLang=en and install it. You might need to uninstall the Beta framework.

 

13.              After you install the .NET Framework 2.0 you need to configure the virtual directory with Asp.NET 2.0. To do this, open IIS Manager right-click the virtual directory DotNetNuke_2 under the Default Web Site, and select Properties. A dialog appears, select ASP.NET tab and specify the ASP.NET version as 2.0.50727. Click Apply and OK.

 

 14.              Now refresh/browse the url http://localhost/Dotnetnuke_2

It helps to know how to setup it up for the intranet and internet too....

Check my post at http://forums.asp.net/1155707/ShowPost.aspx that jeff answered.

Hey!!! I thought I answered it... :)

Hey! You did!

But there is one importante detail about those "alias" that keept me from deploy my site. DNN need to know the url name, for localhost or the live site with the domain info. Jeff told me that, so I thought that the info was a "plus" for your amazing post. Lots of detail and images.

Thanks

adelinoaraujo wrote:

Hey! You did!

But there is one importante detail about those "alias" that keept me from deploy my site. DNN need to know the url name, for localhost or the live site with the domain info. Jeff told me that, so I thought that the info was a "plus" for your amazing post. Lots of detail and images.

Thanks

 

lol user confusion...

Thanks for your helpful post. 

Am attempting to installing DNN 4.0.2 and have SQL Server 2005 on my local machine.  I use Windows XP SP2 which has a different sharing/security screen than you and the Installation Guide use (you show Win 2000/2003?).  Users available in XP in the MMC Computer Management applet are: 1) my Windows administrator login (sharnish) plus 2) IUSR_<localhost> and 3) ASPNET.  

A) What adjustments to Users/Permissions are required for installation under Win XP, IIS 5?

B) How will Users and Permissions need to be adjusted when I upload DNN 4.0.2 to my shared hosting environment?

Thanks very much.

As a follow-up, the user "ASPNET" is apparently the Windows XP alternative for the Network Services user you specify.  This account is created when ASP.NET is installed.  I have added this user to the DotNetNuke database in SQL Server 2005. The Win XP password for this account cannot be viewed or changed.  Is this the account needed for DNN 4.0.2 and how is the web.config database string set for this user?  Or am I needlessly going around in circles? Thanks again.

A) Give the ASPNET user Modify permissions to the DNN directory

B) Depending on the OS at your host you will need to have the same modify permissions to user ASPNET or NETWORK SERVICE

sharnish wrote:

As a follow-up, the user "ASPNET" is apparently the Windows XP alternative for the Network Services user you specify.  This account is created when ASP.NET is installed.  I have added this user to the DotNetNuke database in SQL Server 2005. The Win XP password for this account cannot be viewed or changed.  Is this the account needed for DNN 4.0.2 and how is the web.config database string set for this user?  Or am I needlessly going around in circles? Thanks again.

Depending on your SQL installation use a Windows Account or a SQL Account for the DNN DB . This account is used  by DNN to access the DB and create the tables (Hence the DB_owner requirement). Don't confuse this DB account with the file system account used to give ASPNET permissions to create and manipulate files in the DNN Directory.

"A) Give the ASPNET user Modify permissions to the DNN directory"

Sorry to be dense, but how do I do this with Win XP?  In the directory's Properties applet in XP there are only 4 tabs: General, Sharing, Web sharing, and Customize.  There is no Security tab as illustrated in the example above.  I see the ASPNET user in Computer Management, but am at a loss at granting permissions to the directory. If I try going through IIS (ver 5) the user available is IUSR_<localhost> using annonymous access.  Do I do it here? Thanks much.

Please use MSFT KB to search for "Windows XP Permissions" I remember there was a specific set of steps to enable the tab to appear, but don't remember off the top of my head.

OT and sincere advise. Use search features (here and everywhere else) as much as you can, it is always good to come here at the forums havng done your homework first. Don't take it the wrong way. While members are here to receive and give help, there are things you can and should solve on your own.