I don't know why that might occur.  But did you realize that you don't even need to open the DNN project to create a module?  If you aren't changing DNN then why open the project?  If you create a WAP project and just reference dotnetnuke.dll you will be fine.

Oscar

---

I always develop modules inside the desktopmodules folder, i.e. inside the web site. For WSP, you don't need a solution, simply create your code, place your classes inside your /app_code sub folder (you need to add to subdirectories section in web.config) and you may run and debug w/o compile or limitations. If you create a WAP module, use your own solution file inside the module folder or just above in the owner folder (ideal structure would be /desktopmodules/ownername/modulename). If you'd like to inspect and debug into the DNN library code, you may open the DNN solution, but before touching it the first time with VS, open the .sln file with a text editor, search for "localhost" and adopt the path according to your constallation. HTH

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN