Source Control with Branching and VS support?
-
Hi, We are using Synergy by telelogic atm. been using it for the past 4 years now, and although initially it was a pain in the backside, now I have Build Manager rights :D, I am a lot happier using it! It does branching and Merging pretty well, but its a steep learning curve, not quick(at least not if you have mammoth projects), the GUI is horrendous, and integration with VS could be better. Oh and apparently it is expensive for licenses. Apart from that though, it might be worth a look!
-
Does anyone know of a good source control that has/is: >Branching and Merging >Shallow learning curve >speedy >Good windows tools OR a worthwhile VS plugin I'm looking at subversion (ok, but seems slow), Team foundation (too much - and HOW MUCH???) & Git, but i don't know enough! At the moment we are using the flagship of the microsoft line - SourceSafe! It's fine for most of our little one-man web projects, but for multi-dev use? erm..... No. We're currently working on a project that is different on production, staging and dev. Different bits are added at different times, some things are pushed to production, some things not.... blergh! So, i need a good, easy to use, source control with branching/merging. Over to you....
Thanks for all of the comments. For the moment, it looks like we'll go with the SVN / TortoiseSVN route. If we need to then we'll probably get the VisualSVN client, but in these economic climates.....Maybe we'll just stick with the tortoise! Cheers again!
-
Rob Caldecott wrote:
VisualSVN + AnkhSVN + TortoiseSVN.
+1 on that recommendation. That's our combination. We host the Subversion repositories on Linux/Apache, which mitigates the speed issue somewhat. The biggest slowdown for us is network bandwidth when communication with the repository is required.
-
Thanks for all of the comments. For the moment, it looks like we'll go with the SVN / TortoiseSVN route. If we need to then we'll probably get the VisualSVN client, but in these economic climates.....Maybe we'll just stick with the tortoise! Cheers again!
Che Mass wrote:
If we need to then we'll probably get the VisualSVN client, but in these economic climates.....Maybe we'll just stick with the tortoise!
We've found that TortoiseSVN will handle about 95% of what we want to do on a daily basis. Where a VS plugin (AnkhSVN, VisualSVN) helps greatly is when you need to rename or move stuff in your project. Using TSVN alone, you have to either do the rename/move in Windows Explorer, and then adjust your Visual Studio project, or do it in Visual Studio and then try to figure out how to make TSVN view it as a move instead of a delete and add of a brand new file. Using the plug-in (we use AnkhSVN because it's open-source and free, but VisualSVN is based on TortoiseSVN), it's a matter of simply doing the move/rename in the Visual Studio Solution Explorer.
-
Does anyone know of a good source control that has/is: >Branching and Merging >Shallow learning curve >speedy >Good windows tools OR a worthwhile VS plugin I'm looking at subversion (ok, but seems slow), Team foundation (too much - and HOW MUCH???) & Git, but i don't know enough! At the moment we are using the flagship of the microsoft line - SourceSafe! It's fine for most of our little one-man web projects, but for multi-dev use? erm..... No. We're currently working on a project that is different on production, staging and dev. Different bits are added at different times, some things are pushed to production, some things not.... blergh! So, i need a good, easy to use, source control with branching/merging. Over to you....
We have a team of 6 devs and we are using SourceGear Fortress. Fortress takes Vault and adds work item tracking and build server integration. One of our devs has used many other systems; Clear Case, CVS, Subversion, and TFS and he believes SourceGear is the best. I implemented SCM at our company and through my many evals, SourceGear had the easiest product to install, configure and manage. It was also the least expensive commercial option. We have had a couple of minor issues but support was very helpful. They provide a good SDK and API to write custom tools for builds and various management operations.
-
Che Mass wrote:
If we need to then we'll probably get the VisualSVN client, but in these economic climates.....Maybe we'll just stick with the tortoise!
We've found that TortoiseSVN will handle about 95% of what we want to do on a daily basis. Where a VS plugin (AnkhSVN, VisualSVN) helps greatly is when you need to rename or move stuff in your project. Using TSVN alone, you have to either do the rename/move in Windows Explorer, and then adjust your Visual Studio project, or do it in Visual Studio and then try to figure out how to make TSVN view it as a move instead of a delete and add of a brand new file. Using the plug-in (we use AnkhSVN because it's open-source and free, but VisualSVN is based on TortoiseSVN), it's a matter of simply doing the move/rename in the Visual Studio Solution Explorer.
Can anyone suggest a good write-up/tutorial on SVN with VS? Cheers Terry
-
Does anyone know of a good source control that has/is: >Branching and Merging >Shallow learning curve >speedy >Good windows tools OR a worthwhile VS plugin I'm looking at subversion (ok, but seems slow), Team foundation (too much - and HOW MUCH???) & Git, but i don't know enough! At the moment we are using the flagship of the microsoft line - SourceSafe! It's fine for most of our little one-man web projects, but for multi-dev use? erm..... No. We're currently working on a project that is different on production, staging and dev. Different bits are added at different times, some things are pushed to production, some things not.... blergh! So, i need a good, easy to use, source control with branching/merging. Over to you....
Definitely subversion and TortoiseSVN. No issue with performance and these are full-featured free solutions. Also there is AnkhSVN (I'm using v2.0) which is a VS integration plugin. It is easy to use and I never had any issue with it, and it is not really necessary, TortoiseSVN does a good job by itself. The learning curve of TortoiseSVN is really short. Here is an article that demonstrates that: Getting started with Subversion - Peter's Gekko[^] I hope this helps. Regards, Fábio
-
Can anyone suggest a good write-up/tutorial on SVN with VS? Cheers Terry
Here: Getting started with Subversion - Peter's Gekko[^] I hope this helps. Regards, Fábio
-
Does anyone know of a good source control that has/is: >Branching and Merging >Shallow learning curve >speedy >Good windows tools OR a worthwhile VS plugin I'm looking at subversion (ok, but seems slow), Team foundation (too much - and HOW MUCH???) & Git, but i don't know enough! At the moment we are using the flagship of the microsoft line - SourceSafe! It's fine for most of our little one-man web projects, but for multi-dev use? erm..... No. We're currently working on a project that is different on production, staging and dev. Different bits are added at different times, some things are pushed to production, some things not.... blergh! So, i need a good, easy to use, source control with branching/merging. Over to you....
SourceGear Vault. Zero learning curve. Great VS Studio plug-in. SQL Server repository for your code. Includes tool to import your existing Visual Source Safe database. Free single user license. Good price for additional users. Overall bullet-proof.
-
Che Mass wrote:
Team foundation (too much - and HOW MUCH???)
Of all the suggested alternatives VSTS (Visual studio team system) is probably the most hassle free, feature complete (and probably most expensive too). I have been using it for quite some time now (in a team of 4 to 6 devs) and it has been smooth sailing ever since. Support for Branching and merging is excellent too. My favourite feature in VSTS is the ability to shelve what you are doing now and start working from scratch with the version on the source control without losing the current changes (hope this makes sense). Cheers, SDX2000.
The best way to accelerate a Macintosh is at 9.8m/sec-sec - Marcus Dolengo
I've also heared about this new Shelving feature, and I see it's really something I would regulary use. But where is the difference between - Putting something "on shelve" - Putting it in an new branch. Is it just the benefit, nobody else sees my shelve ? Or minor adminstativ overhead?
-
Here Here!!!
Tim Friesen
-
We have used VSS for about 10 years - we had some horrible thing called PVCS before that. It has its quirks and it works better if the source database is regularly pruned, but for us - a dev team of 5 - it does the job. It got a whole lot easier when Visual Studio brought in the 'change source control' functionality (about 2003/2005, can't remember exactly). It was manual editing of the project file after a branch before that! I guess we really ought to investigate the alternatives, but we are fairly happy with what we have, and there are other priorities...
-
Does anyone know of a good source control that has/is: >Branching and Merging >Shallow learning curve >speedy >Good windows tools OR a worthwhile VS plugin I'm looking at subversion (ok, but seems slow), Team foundation (too much - and HOW MUCH???) & Git, but i don't know enough! At the moment we are using the flagship of the microsoft line - SourceSafe! It's fine for most of our little one-man web projects, but for multi-dev use? erm..... No. We're currently working on a project that is different on production, staging and dev. Different bits are added at different times, some things are pushed to production, some things not.... blergh! So, i need a good, easy to use, source control with branching/merging. Over to you....
I'm in the process of switching from subversion to Mercurial (http://www.selenic.com/mercurial/wiki/) and am liking it quite a bit so far. Plus, the Tortoise client for Windows is almost exactly the same for both.
-
Does anyone know of a good source control that has/is: >Branching and Merging >Shallow learning curve >speedy >Good windows tools OR a worthwhile VS plugin I'm looking at subversion (ok, but seems slow), Team foundation (too much - and HOW MUCH???) & Git, but i don't know enough! At the moment we are using the flagship of the microsoft line - SourceSafe! It's fine for most of our little one-man web projects, but for multi-dev use? erm..... No. We're currently working on a project that is different on production, staging and dev. Different bits are added at different times, some things are pushed to production, some things not.... blergh! So, i need a good, easy to use, source control with branching/merging. Over to you....
We are using Accurev - branching/merging are a piece of cake, and it works well with multiple devs. Pretty shallow learning curve for devs - a little more for Admin (some of the functions are tricky to find in the GUI).
-
Does anyone know of a good source control that has/is: >Branching and Merging >Shallow learning curve >speedy >Good windows tools OR a worthwhile VS plugin I'm looking at subversion (ok, but seems slow), Team foundation (too much - and HOW MUCH???) & Git, but i don't know enough! At the moment we are using the flagship of the microsoft line - SourceSafe! It's fine for most of our little one-man web projects, but for multi-dev use? erm..... No. We're currently working on a project that is different on production, staging and dev. Different bits are added at different times, some things are pushed to production, some things not.... blergh! So, i need a good, easy to use, source control with branching/merging. Over to you....
I work at a 150+ devcount site; we use VSTS/TFS2008, a necessity given the volume of projects and developers. But ... we are also running into ceiling issues with branching/merging and need MS consultancy to repair. TFS is by far the most mature source control system, but is actually not mature enough yet for flagship enterprise usage. Undoubtedly will become so in Rosario++. If you use VSS now and are in a 10+ developer situation, I still would advise migrating to TFS. You will however need someone (+ backup) with more than just suferficial knowledge of the workings of merging and branching. Tips and tricks are required, e.g. when it comes to issues due to renames, deletions, moves, simultaneously in changesets, branching for overlapping release management, component version integration issues, etc. etc.
Regards, Arjan Keene
-
Does anyone know of a good source control that has/is: >Branching and Merging >Shallow learning curve >speedy >Good windows tools OR a worthwhile VS plugin I'm looking at subversion (ok, but seems slow), Team foundation (too much - and HOW MUCH???) & Git, but i don't know enough! At the moment we are using the flagship of the microsoft line - SourceSafe! It's fine for most of our little one-man web projects, but for multi-dev use? erm..... No. We're currently working on a project that is different on production, staging and dev. Different bits are added at different times, some things are pushed to production, some things not.... blergh! So, i need a good, easy to use, source control with branching/merging. Over to you....
Well we use Surround from Seapine and it's an amazing tool much better then Source Safe. http://www.seapine.com/surroundscm.html regards, :-D
-
Does anyone know of a good source control that has/is: >Branching and Merging >Shallow learning curve >speedy >Good windows tools OR a worthwhile VS plugin I'm looking at subversion (ok, but seems slow), Team foundation (too much - and HOW MUCH???) & Git, but i don't know enough! At the moment we are using the flagship of the microsoft line - SourceSafe! It's fine for most of our little one-man web projects, but for multi-dev use? erm..... No. We're currently working on a project that is different on production, staging and dev. Different bits are added at different times, some things are pushed to production, some things not.... blergh! So, i need a good, easy to use, source control with branching/merging. Over to you....
We're using Subversion with TortoiseSVN and VisualSVN for VS integration - we found that doing as much as possible from within Visual Studio (using VisualSVN) seems to be very intuitive and reduces the learning curve significantly - We haven't worked with branching/merging much, though... We have not noticed any speed issues, but we do have very good bandwidth on the local network...
-
Does anyone know of a good source control that has/is: >Branching and Merging >Shallow learning curve >speedy >Good windows tools OR a worthwhile VS plugin I'm looking at subversion (ok, but seems slow), Team foundation (too much - and HOW MUCH???) & Git, but i don't know enough! At the moment we are using the flagship of the microsoft line - SourceSafe! It's fine for most of our little one-man web projects, but for multi-dev use? erm..... No. We're currently working on a project that is different on production, staging and dev. Different bits are added at different times, some things are pushed to production, some things not.... blergh! So, i need a good, easy to use, source control with branching/merging. Over to you....
I've never used it, but you could try 'Vault' (http://www.sourcegear.com) We used TFS, and it's pretty good... but then pricing wasn't an issue for us, and although its' good and a alot better than source safe, has some nice features etc. some of the implementation details still leave a lot to be desired.
-
Does anyone know of a good source control that has/is: >Branching and Merging >Shallow learning curve >speedy >Good windows tools OR a worthwhile VS plugin I'm looking at subversion (ok, but seems slow), Team foundation (too much - and HOW MUCH???) & Git, but i don't know enough! At the moment we are using the flagship of the microsoft line - SourceSafe! It's fine for most of our little one-man web projects, but for multi-dev use? erm..... No. We're currently working on a project that is different on production, staging and dev. Different bits are added at different times, some things are pushed to production, some things not.... blergh! So, i need a good, easy to use, source control with branching/merging. Over to you....
Used SourceSafe for 8 dev team, back before MS acquired it. Good, but I also recall replicating the database to effect release "branches". Back then it used a binary gobblygook database format, that self-corrupted (!) over time. Wouldn't use it by choice ever again. Where I work now we use CVSnt backserver with WinCVS (v1.3 -- later clients are too confusing) as a windows client for a 16 dev team (12 Lin, 3 Win). Steep, and imperfect (lacks file rename/move and dir hierarchy versions), but OK (branch/merge good). CVS is RCS based, so checkin/label/branch are slow because entire repository file must be rewritten, but chechouts are fast. Any RCS-based control will suffer similarly (PVCS used to be RCS based, dunno what it is now). A big advantage of RCS is that data is kept in the clear, making recovery possible with a text editor worst case. Don't know about others, but I know you can run CVS through a ssh tunnel when away from the office. That's convenient when you're working code at home or on the road.
patbob
-
Does anyone know of a good source control that has/is: >Branching and Merging >Shallow learning curve >speedy >Good windows tools OR a worthwhile VS plugin I'm looking at subversion (ok, but seems slow), Team foundation (too much - and HOW MUCH???) & Git, but i don't know enough! At the moment we are using the flagship of the microsoft line - SourceSafe! It's fine for most of our little one-man web projects, but for multi-dev use? erm..... No. We're currently working on a project that is different on production, staging and dev. Different bits are added at different times, some things are pushed to production, some things not.... blergh! So, i need a good, easy to use, source control with branching/merging. Over to you....
Definitely you should take a look at Perforce - it is absolutely the best (but costs rather hefty $). We are using Subversion now (people were recommending it, and we thought we will save some money by not using Perforce), and I cannot say that it is very bad, but at the same time I am not sure that I will use it in my next project - slow, big repository, rather rudimentary tools (TortoiseSVN is worse than ancient WinCVS, and not even comparable to Perforce), many small issues (especially with branching/merging/reintegration).