Sunday, May 9, 2010

Installing DotNetNuke (DNN) under Windows 7

Many of my students at BCIT have asked me for help with the installation of DotNetNuke (DNN) under IIS 7 on Windows 7. This is a little bit different from previous Windows operating systems because of the security model and the default application pool account that IIS 7 uses.

The prerequisite is to have SQL Server Express and the IIS feature activated on your Windows 7 environment.

Here are the steps that I recomended to my students:

  1. Download DNN from and install it in a directory like c:\DotNetNuke
  2. Copy "release.config" to "web.config" in the root directory of DNN
  3. In IIS 7 add a "New Application" under the "Default Web Site" pointing to the location where DNN was installed (like c:\DotNetNuke).
  4. Create a new application pool named "dnn" in IIS 7. Changed "Load user profile" property to "False" by clicking on the "Advanced Settings" link of the "dnn" application pool.
  5. Set the application pool for your "Default Web Site" to "dnn" by clicking on the "Basic Settings" link
  6. Give the physical directory of your site (I.E. c:\DotNetNuke) full access permission to account "IIS AppPool\dnn"
  7. Point your browser to http://localhost/DotNetNuke. If all goes well you will enter the DNN configuration wizard.

Vancouver Silverlight User Group (VanSLUG.NET) Launch

On May 5, 2010 I launched the Vancouver Silverlight User Group which I named VanSLUG. The group's web site is at The first meeting was held at BCIT and was co-hosted by VanSPUG, .netBC, and VanSLUG. Habaneros sponsored the snacks. We had attendance of over 80 people.

The speaker was Laurent Duveau, who is a Silverlight MVP from Quebec City. He gave a talk entitled "Silverlight 4 Business Applications". His presentation was very well received and he got many questions from the audience. He has blogged about the event at:

You can download his presentation and examples from the above site.

Thursday, May 6, 2010

Getting FTP to work on Windows 2008 server

I installed the FTP server feature on a Windows 2008 server. However, when I tried to connect from an FTP client, I consistantly got an error suggesting that the directory could not be listed, even though authentication went through. I checked the Windows Firewall setting and found that "FTP Server" was indeed checked in the exceptions list. A quick google saved my day. You can configure the Windows Firewall to allow non-secure FTP traffic with these two command-line commands:

1) Open port 21 on the firewall
netsh advfirewall firewall add rule name="FTP (no SSL)" action=allow protocol=TCP dir=in localport=21
2) Activate firewall application filter for FTP (aka Stateful FTP) that will dynamically open ports for data connections
netsh advfirewall set global StatefulFtp enable

Kudos to this site: