Hey Geoffrey,

Here is what my setup is - maybe that will help:

First, I have a DotNetNuke (source version) development site set up. This is http://localhost/DotNetNuke @ c:\inetpub\wwwroot\DotNetNuke\Website

I then create a new module inside the DesktopModules folder of the website -> c:\inetpub\wwwroot\DotNetNuke\Website\DesktopModules\MyModule

In the module's project files, I set the build output to the bin directory of the website ("..\..\bin") and I set it to launch the website http://localhost/DotNetNuke when you run the project.

After you create a module definition within your DotNetNuke site, you can either run your site, or attach to process, and be debugging your module, while running your dotnetnuke site.

Hope that helps!

Take care,

Ian

Hi Tony and Ian

Thank you both for your answers. My problem is that I have a suite of 14 modules, all Web Application Projects, under one VS2008 solution and each is divided into the aspx pages and a separate sqldataprovider. So they compile to 28 dlls.

When I attach to process, 28 copies of the ASP.NET Development Server open but not the DNN Web Site in IIS. How should I configure each projects MyProject Web tab? If I select Use IIS WEb Server and give my project URL (http://localhost/DNNDevEnv) it first tells me that I have to configure  aVirtual Directory (it is already an application) and then tells me I can't. Any suggestions?

Regards

Geoffrey

PS PowerDNN host my site www.yalaworld.net and I am very pleased with your service.