Hi Thomas,
Your concern for version control is justified as configuration control becomes quite important in large teams which are working on diverse technologies and different product releases.
Although, I could not find any guidelines on whether to use a single version control system for .net and ABAP source code or to use 2 different version contrl systems, but from my personal experience I can suggest that you must try to <b>standardize on 1 version control system</b> for all code. Having 2 different version control systems may defeat the whole purpose of version management. Also consider that you may have other project artifacts to store besides the source code.
In our case the ratio of .net development to ABAP developement was roughly 7:3. There was also a small part of the application which was in Java. We decided to use MS Visual Source Safe because it was well integrated with MS Visual studio and the MS developers were hands on with it. The ABAPers and Java coders could start using VSS after some initial inputs. For every build release we baselined the .net, Java, PL/SQL and tbe ABAP code in a separate area under VSS.
If the ABAP component in your code in larger you may also seriously consider using version control provided by SAP.
Kindly note that you may have to adpapt the approach to better suit your setup. I would be glad to hear your experience on the approach you take.
Cheers
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.