this is a tough one to answer as theres no "right" answer, as it depends on lots of factors. One common way that people do this is to pick the minimum version of DotNetNuke they intend to support and download that version of DotNetNuke (the install release - there is rarely ever any need to use the source version of DotNetNuke). You then create a visual studio solution and add that website to it.

If you're using vs.net templates such as http://www.dotnetnuke.com/Resources/V... , then they support packagin builds, so it means that if you have a new module you create a new project based on this template and set it to build to a folder within DesktopModules in debug mode, and set the output of release mode to copy the zip files over to the install/modules folder. That way you can download all the code from TFS and simply install the website and then any of the modules. You can then update any of the module code and do a build and the updated dll(s) will be copied to the website bin folder (the updated ascx etc are already in the correct place) allowing you to test. Obviously once the website is installed you can simply open the vbproj/csproj file for the module and not have to have the full solution open.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US