What is a good source control for VS 2013
-
TFS Express only support 5 developers. He'll need the full version, which is not free.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak -
The full edition is $499 per user, (visual studio itself is only about $510), I am looking for something simpler and much cheaper. I also want something that I can still use when I upgrade to my next visual studio version.
-
Comparison of revision control software[^]
thatraja
Code converters | Education Needed No thanks, I am all stocked up. - Luc Pattyn When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is - Henry Minute
excellent link thatraja, thanks!
-
I am planning to upgrade our visual studio editions from 2010 to 2013 professional (without MSDN). Our current 2010 solution still works with visual source safe 2005 (!!!), it works beautifully, but I find it too old to continue with it. What is the best practice, free or low cost solution for source control of a development team these days? - About 12 programmers - Visual studio 2013 only. Previously I was put off by team foundation because of cost, and complicity. I only have to keep versions, and make sure that two people wouldn't work on the same file at the same time. Hope someone can shorten my learning process by sharing his/her own experience.
Leo Muller Rap wrote:
make sure that two people wouldn't work on the same file at the same time
That's an old concept of Visual Source Safe, where all your local files were read-only before you checked them out from VSS, and thus locked them there. Most souce control systems do not do so: you edit your local copy, and at check-in the source control checks if a merge is required or not - and it hardly ever happens to be required.
-
Leo Muller Rap wrote:
make sure that two people wouldn't work on the same file at the same time
That's an old concept of Visual Source Safe, where all your local files were read-only before you checked them out from VSS, and thus locked them there. Most souce control systems do not do so: you edit your local copy, and at check-in the source control checks if a merge is required or not - and it hardly ever happens to be required.
Thanks, that piece of information is usefull to hear, because ininitally I was resistant to that approach, but if that is what really works it is just about getting to the idea of working a bit differently.
-
I am planning to upgrade our visual studio editions from 2010 to 2013 professional (without MSDN). Our current 2010 solution still works with visual source safe 2005 (!!!), it works beautifully, but I find it too old to continue with it. What is the best practice, free or low cost solution for source control of a development team these days? - About 12 programmers - Visual studio 2013 only. Previously I was put off by team foundation because of cost, and complicity. I only have to keep versions, and make sure that two people wouldn't work on the same file at the same time. Hope someone can shorten my learning process by sharing his/her own experience.
Hello, Perforce is a good one : http://www.perforce.com/company/newsletter/2012/02/perforce-now-free-20-users[^] TFS, Git, CVS, SVN or Visual SourceSafe are good too ;)
Light or darkness, we must choose ...
-
Hello, Perforce is a good one : http://www.perforce.com/company/newsletter/2012/02/perforce-now-free-20-users[^] TFS, Git, CVS, SVN or Visual SourceSafe are good too ;)
Light or darkness, we must choose ...
I wouldn't use "Visual SourceSafe" and "good" in the same sentence unless it was "good for nothing" or "good for headaches".
-
I wouldn't use "Visual SourceSafe" and "good" in the same sentence unless it was "good for nothing" or "good for headaches".
Two key points to keep in mind with SourceSafe : - Manage check-in/check-out through Visual Studio exclusively - Use project references everywhere you can. But I agree a little with you, it is not as efficient as the others ;)
Light or darkness, we must choose ...
-
Two key points to keep in mind with SourceSafe : - Manage check-in/check-out through Visual Studio exclusively - Use project references everywhere you can. But I agree a little with you, it is not as efficient as the others ;)
Light or darkness, we must choose ...
Ahmed Bensaid wrote:
Two key points to keep in mind with SourceSafe :
- Manage check-in/check-out through Visual Studio exclusively
- Use project references everywhere you can.Three points actually. The third is: - it's now obsolete.
Kevin
-
Ahmed Bensaid wrote:
Two key points to keep in mind with SourceSafe :
- Manage check-in/check-out through Visual Studio exclusively
- Use project references everywhere you can.Three points actually. The third is: - it's now obsolete.
Kevin
I agree ;)
Light or darkness, we must choose ...
-
Ahmed Bensaid wrote:
Two key points to keep in mind with SourceSafe :
- Manage check-in/check-out through Visual Studio exclusively
- Use project references everywhere you can.Three points actually. The third is: - it's now obsolete.
Kevin
Good article Irfan >>~moving <<code can >> Dignity and ^^~…+<<****
-
I agree ;)
Light or darkness, we must choose ...
A bit late, but I'd also like to add that the 'Safe' part of VSS is a lie: VSS is not transaction-based and therefore conceptually prone to data loss. From my experience, even in small teams, you can expect damaged (i. e. lost) data several times a week. VSS is not secure either, as the data is no more secure than the file system it is stored in.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)