How to Install DotNetNuke 4.3.x
|1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11|
Gee, It’s About Time! Let’s Install DotNetNuke
Okay, well, installing 4.3.5 was remarkably easy—for those that have installed 2.x and 3.x before, at least. I used the install zips. As stated above, I think it’s important to do it in this order. You really do not want IIS or ASP.NET 2.0 messing with your web.config, until you’ve made the changes you want to make to the web config, and until after you have added the necessary permissions.
1. Download the 4.3.5 install zips. Navigate to this URL:
http://www.dotnetnuke.com/tabid/125/default.aspx, then click on the ‘DotNetNuke 4.3.5 Install’ link. If you want the complete sources, then click on the ‘DotNetNuke 4.3.5 Source’ link instead. And if you want to be able to build modules and skin objects, etc, then also download the ‘DotNetNuke 4.3.5 Starter Kit’.
2. Again, make sure you have IIS installed. Because ASP.NET 2.0 makes changes to IIS, it won’t make them if IIS is not installed. Once you know IIS is installed (you can verify the IIS install by opening your Control Panel, choose Administrative Tools, and verify that ‘Internet Information Services Manager (IIS) is one of your administrative tools, then make sure you have ASP.NET 2.0 Installed. How can you tell? Well, unless you’ve uninstalled it, you can go to C:\WINDOWS\Microsoft.NET\Framework\ and you should see a folder named ‘v2.0.50727’. You can also open up IIS, open up a current website or virtual folder, click on the ASP.NET tab, and see if ‘ASP.NET v2.0.50727’ is an available option. Then go to Windows Update and make sure you download any updates.
3. Create a folder for your virtual directory/website. You can call it anything you want. However, if you name it different than ‘DotNetNuke_2’, and you want to install and debug the source, you will have to open and edit the dotnetnuke.sln and dotnetnuke.webproj files, and change any urls that point to http://localhost/dotnetnuke to http://localhost/myvirtualfoldername.