|
Post by alpaholic on Mar 19, 2007 14:11:22 GMT
One for the engineers.
I'm investigating Source Control/Configuration management for large teams over multiple sites. Effective branching must be possible & data integrity is important so VSS is really not up to the task.
This is for both Documents and Source code so Plug in to Visual Studio 2005 & VS .net 2003 would be nice.
Any thoughts?
|
|
|
Post by beeblemaster on Mar 19, 2007 15:33:32 GMT
I was supposed to do a similar thing for February but never had time.... (I wonder if my post count increased in February) I'm using VSS at the moment as it's better than nothing but trying to get all members of the team using it. Don't know why I've been asked to look into it though, when we're just the little fish and there's a great big development team out there usiing 'something'... but then that's in India. Fancy working together?
|
|
|
Post by alpaholic on Mar 19, 2007 15:42:21 GMT
Don't know why I've been asked to look into it though, when we're just the little fish and there's a great big development team out there usiing 'something'... but then that's in India. Fancy working together? I'll let you know anything I find. As you say our solution is dependant on others so I have no idea why we're researching. Still, all marketable knowlege for me!
|
|
|
Post by Welsh Ade on Mar 19, 2007 16:49:46 GMT
now in english please and without the jargon. You want what, for what
|
|
|
Post by teejayexc on Mar 19, 2007 17:38:45 GMT
Personally I use head and shoulders, seems to work for me anyway. Trev
|
|
|
Post by redline on Mar 20, 2007 16:48:03 GMT
SVN (subversion) all the way.
we used to use VSS but it almost drove us insane.
There is a VS pluggin available but personally i prefer to use the Explorer extension Tortoise.
HTH
AB
|
|