Mike,

We use VS2010 & TFS.  We have a TFS project that has our set of shared libraries including our subsonic DAL.  So, that project has a VS solution with multiple projects.  Then we have a DNN TFS project where we develop custom modules & skins.  So, that has another VS solution with multiple projects.  We also include the subsonic DAL project from our shared libraries.  One note, we use the install version of DNN and we do not keep that in source control.   Yes, we do use Chris Hammond's starter kit..  So, when we create a new module it goes into the desktopmodules folder.    then we add a reference to the subsonic DAL which will copy the subonic DLL and DAL dll to the dnn bin directory.  So your module will always pull the latest version of the DLL.  If you make a change to the DAL then it might break another module, you just have to be aware of that.  We added the subsonic sections to DNN web.config so we don't need it with the DAL project.  For the DAL project, we generate our base classes from the command line manually and then just drag them into the DAL project. 

That really sums it up.  It took a little to get it set up right but now it works great.  One thing, I never use the install packages created from Chris's starter kit to install the module on the local DNN instance.  I always set them up manually through the portal.  I don't want to accidentally over write anything.

Robert