can someone help?

I start with an empty solution and add the DNN website. Then I add my custom module projedts (I don’t use Web Application Projects). I add a project reference in the DNN website to each of my projects, this will copy over the .dll. In the build configuration I disable the compilation of the DNN website. VS 2005 stores all project settings for the website in the solution file. This means you can use a single DNN website with multiple module projects in separate solutions. The project dependencies won’t affect the site outside of the solution. Personally, I think the VS 2005 handling of websites is much better than VS 2003.

I’ve found that compiling the entire DNN solution is very slow, however unless you’re modifying the core you shouldn’t have to compile DNN with your projects.

I also recommend the following:
1) Disable the scheduler in both the web.config and host settings.
2) Uninstall modules that you don’t need.
3) Delete unnecessary modules from the first page.
4) Login and choose remember password so you don’t have to login every debug session.

Brian

---

Qualtiy DotNetNuke modules and custom development; we've been serving the DNN community for over 2 years and have hundreds of satisfied customers. Let us serve you today.