I'm hoping we can get some advice on the subject of setting up source control for internal modules development of DNN modules.  I've already found a few articles and posts related to this subject, but they are a bit dated or assume that the module source is open and would be posted on codeplex.

Here is what we want to do:

• Allow multiple developers in geographically diverse areas develop against a corporate DNN "dev" instance.
• Use internal source control (we're licensed for Team Foundation Server)
• We use a modified version of Christoc's module template and love love love the ability to us MSBuild to automate module packaging.  We'd really like to keep this.
  • Related to this, each module has it's own solution and project file
• Ideally, we want to code against that dev instance because:
  • Project managers and project stakeholders want to "see" module dev progress
  • It's backed up and secure
  • It keeps all of our code in a single managed place (solving both the "what if my laptop gets run over by a bus" or I decided to work somewhere else" issues.)

It seems like TFS wants us to dev locally and then "check in" code to TFS.  I guess we're looking for some guidance on the best way to setup TFS, local dev and DNN so we can all code either against that single box or our local codes are checked in and build up on the dev machine.

Admittedly, TFS is new to us to we're pecking away at it but hoped a community member (or DNN employee) might have some "this worked and this didn't" advice and guidance for us.

Thanks in advance for any information on this one.