I am seeing solutions on how best to manage version control of .NET applications (multi developer) inline with components outside of the .NET application; such as web services, databases, etc.,?
For years, our projects have been worked on by one developer at a time - typically they're either straight forward or small solutions that haven't needed more than one developer, so version control is rather well managed by (originally) SourceSafe and (in the past couple of years) SubVersion. We're using Visual Studio 2005 at the moment; migrating to newer versions would be quite a big task.
But, more recently we're team working on a couple of much bigger projects with a couple of UK developers and a small team in our offshore office and whilst we're managing well with SubVersion, it's a bit of a pain for our Release Management (RM) as we need to compile different versions into a release, not so straight forward with a .NET application and SVN.
The development teams for each component use SubVersion successfully, but it's how best to coordinate it all back for a production release that we're struggling with.
I would be interested in hearing of "successful" solutions that others have implemented.
Is it any easier with more recent versions of Visual Studio?
Any advice appreciated.
Last edited by fullingdale; December 17th, 2010 at 10:31 AM.
Reason: Rephrased some of the question