In my VS 2008, I have the "Dotnetnuke Compiled Module" template...under "Web". Only for VB, but I don't think a C# one comes with any of the DNN downloads.
The template works, but, after it runs a creates the project files it does error out with a message like:
"The local IIS URL http://localhost/Dotnetnuke_2 specified for the Web project TestModule has not been configured. In order to open this project the virtual directory needs to be created. Would you like to create the virtual directory now?"
Click yes creates some other error...
However, another posting on this issue somewhere had details on how to manually fix the generated .vbproj file:
If I open the generated file in notepad: "WebWorking2\AdverageousDev2\Website\DesktopModules\TestModule\TestModule.vbproj"
Almost at the very end is:
<WebProjectProperties>
<UseIIS>True</UseIIS>
<AutoAssignPort>True</AutoAssignPort>
<DevelopmentServerPort>4825</DevelopmentServerPort>
<DevelopmentServerVPath>/</DevelopmentServerVPath>
<IISUrl>http://localhost/DotNetNuke_2</IISUrl>
<NTLMAuthentication>False</NTLMAuthentication>
<SaveServerSettingsInUserFile>False</SaveServerSettingsInUserFile>
</WebProjectProperties>
For my setup, I change the IISUrl line to this:
<IISUrl>http://localhost/AdverageousDev2/DesktopModules/TestModule</IISUrl>
I can then add the project file back into my solution, and continue on with hacking away at code.
I've never used much the full web site starter kit, only this startkit template (and a few other hacks to get a standalone, seperate skeleton module project to work off of).
Most often my solution file has the DotNetnuke website, and one module only. Occassionally I'll debug using the full solution file included with the DNN source download "DotNetNuke_VS2008.sln", and add my module to that.
I prefer working with as few of projects as possible in VS, my 286 computer slows down when I have to work with a bunch 