Source control for different teams?

Need recommendations for this ...

I have 2 teams

  • Developing an Enterprise SOA with InfoPath 2003, BizTalk 2006, MSCRMv3, custom.net2, and a set of web services using VSStudio 2005 with TFS.
  • The web group focused on public sites - using the Adobe Suite, VSStudio 2005.

As mentioned team 1 has TFS: we do not create daily / weekly / nightly / internetworking builds as we do not use this type of methodology, but we do have a custom build / test solution using msbuild built into TFS. (it does other funky stuff like zips for archive, biztalk version / delist, deploys new assemplies in biztalk and renelist from biztalk and full deployment of website and services)

Team 2 has nothing ... except the version archive.

Problems...

  • TFS is expensive
  • Both commands are used to "lock school" source control.
  • need a source of control for different campaigns

Any suggestions - OSS or others wise?

0


source to share


3 answers


svn - can even preserve blocking strategy (if you need), also you can develop all kinds of pre / post commit hooks to automate deployments / tests, etc. Easy to set up and manage.

Some tools and links



+2


source


I would go with TFS for both teams, despite the cost. You already have experience for this product and it supports the blocking model you like.



If cost is an issue, go with SVN for web team, but buy VisualSVN for Visual Studio integration and use TortoiseSVN for Explorer integration. I've found in the past that web teams tend to "get" SVN a little faster, especially with TortoiseSVN.

+1


source


I am working with Subversion , running VisualSVN Server and TortoiseSVN and AnkhSVN for Visual Studio on client development machines, this is a really good setup and it's all OpenSource.

+1


source







All Articles