Hello,

I am currently reading Professional Module Programming by Mitch Sellers. I am stuck at chapter 5 trying to create the GuestbookCS Module.
While installing DotNetNuke I had to configure IIS and create a virtual directory pointing to my DotNetNuke folder, so I was able to run DotNetNuke using the following URL: http://localhost/DotNetNuke.
Now at the module creation process I had to configure the project settings. The book told me to modify the Project URL setting contained inside the web section and set it to http://localhost/DotNetNuke. When I try to save the project settings I get a message telling me, that I have to create a virtual directory. This fails because the virtual directory already exists and is mapped to a different folder location. How can I solve this problem? Which Project URL should I use in this case?

This is the error message I receive when I try to save the project settings:


This is the error message I receive when I try to create a virtual directory:


The DotNetNuke installation folder ist located at C:\inetpup\wwwroot\dotnetnuke and the folder containing the GuestbookCS module ist located at C:\inetpub\wwwroot\dotnetnuke\DesktopModules\GuestbookCS.
I am using DotNetNuke 5.2.3 (Installation Package and Starter Kit) together with Windows 7 Pro, IIS 7 and Visual Studio 2008 Pro.

Thanks for helping me.

Hi I have the same problem, and I am using the same setup as Christoph. I am also following the same book. I have searched the internet but not been successful in finding a solution to my problem. I can add that I am running VS2008 in admin mode (at least thats what it says in the title bar). Temporarily I have just selected the "Use Visual Development Server".

I think a solution might be to open the existing dnn installation, instead of creating a new module...

So click "File" -> "Open" -> "Website" and choose the local dnn website. Then when it is loaded right click the website in solution explorer and choose "Add new item..." and then select the "DotNetNuke Dynamic Module". Configure the module and start creating the custom module.

This seems to work and also when i did this the <dnn:label> in my *.ascx files  were recognised...