Source Version Control
-
See my reply in the same level as yours. Go read it then get AnkhSVN: http://ankhsvn.tigris.org/[^] I have used it with VS 2005 and found it to be worthy of recommendation. It's a nice little add-in.
-
try using perforce. www.perforce.com
_____________________________ www.DaytonaForums.com
-
NOT CVS. One of the biggest piles of crap I've ever used.
Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
-
Source control seems to be a complex process.
█▒▒▒▒▒██▒█▒██ █▒█████▒▒▒▒▒█ █▒██████▒█▒██ █▒█████▒▒▒▒▒█ █▒▒▒▒▒██▒█▒██
You know it really is. I won't even tell you I pretend to understand half of it. Search the lounge a while back someone posted about the source control methods Microsoft used for Vista. I was reading it thinking :omg: that's complex. I really think you just have to moderate your own needs. For guys like us not working in large groups compiling applications in separate builds and then doing team builds weekly source control can be a lot simpler. I have SVN configured very simply and it's very simple to use. The Ankh add-in really takes it a step simpler where it's just *right-click* -> *select action* (check in/out) and keep coding on your merry way. That post I link back to might look complex but if you read through it slowly and carefully you can have SVN up and running in less than 30 minutes which I don't think is to bad for a product that is free. Honestly though, for the type of check in/out you and I need I think VSS 2005 is just fine to. I use it on some of my other boxes and it's never treated me wrong.
-
Subversion is great. We just completed a migration from an old RCS-based system. The conversion with cvs2svn[^] works very well. If you're used to CVS (which isn't bad; SVN is just better) or VSS (which is bad X| ), SVN just takes a little getting used to. The TortoiseSVN on-line documentation is quite good. Bob
-
-
I have spent most of the last week researching and testing different open source source control offerings. We need branched source control with the ability to build to a version as well as being able to integrate with VS2005 and support automated builds. CruiseControl.net gives me the automated builds and can use subversion as the source control. There is a plugin that integrates subversion into vs2005 and it works pretty good so far. I am struggling with the build scripts in CruiseControl.net but I have to accept this since I did not have to pay anything either. I got most of my help from the postings here on CP however there is plenty of help on the web and even free books(pdf). I need to get the environment up and runing by next week so the team can get use to it and so far it is comming together pretty good for open source. Best of luck with the search.
-
I will add a nod for Subversion like most of the other folks. The subversion book http://svnbook.red-bean.com/[^] for getting started.
I'd love to help, but unfortunatley I have prior commitments monitoring the length of my grass. :Andrew Bleakley:
-
It would also be nice if it integrated with VS2005.
█▒▒▒▒▒██▒█▒██ █▒█████▒▒▒▒▒█ █▒██████▒█▒██ █▒█████▒▒▒▒▒█ █▒▒▒▒▒██▒█▒██
Just my opinion but, VS integration is overrated. Esp with quality tools like Subversion. Many end up just using the VS forced view and subset of the tool rather than using the tool as it was meant to be used.
My Blog A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. - -Lazarus Long
-
try using perforce. www.perforce.com
_____________________________ www.DaytonaForums.com
rstum wrote:
though it is really good but not free i guess it starts with 800$ for a licence (first 2 are free)
-Prakash
-
-
Sourcegear Vault -- free for personal usage. I've just migrated from SourceSafe (been using them since the DOS-version). When it comes to integration with VS2005 I have no idea. I keep them separated.
-
If you are working in a single user enviroment you can download and use Sourcegear Vault for free. I installed this on my home pc, and also installed hamachi (www.hamachi.cc) and now i can access my source code from anywhere in the world via my laptop, very convenient! :-D Sourcegear vault also migrates all your existing projects from sourcesafe :mad:(grrr) and integrates well with vs2003 & vs2005. I also use it with the company i work for and have 10 developers using it, 6 of them in another country. excellent product. obviously its not free in a multiuser environment though!:doh:
---Guy H (;-)---
-
NOT CVS. One of the biggest piles of crap I've ever used.
Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
Agreed - I must prefer subversion! Elaine (subversive fluffy tigress)
-
Another vote for subversion. Don't bother trying to integrate it into VS--use Tortoise SVN to integrate into Windows Explorer.
David Veeneman www.veeneman.com
-
NOT CVS. One of the biggest piles of crap I've ever used.
Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
We had CVS shoved down our throats because that is what our offshore developers were using, and we needed to integrate with what they were doing for us. I guess it was seen as the path of least resistance by those on high for us to change rather than getting the offshore guys to change. I must admit, it is possible to do a lot more in CVS that what were were using before (VSS :sigh:), but it is a bas**rd to learn. I think those folks went out of their way to make it complicated. Cheers,
-
Just my opinion but, VS integration is overrated. Esp with quality tools like Subversion. Many end up just using the VS forced view and subset of the tool rather than using the tool as it was meant to be used.
My Blog A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. - -Lazarus Long
Chris Austin wrote:
Just my opinion but, VS integration is overrated.
I disagree. Without (usable) VS integration, you'll never get a VS-based team to fully adopt it. And that's not just for source control, that's anything that needs to be an integral part of the development process. If you work by yourself or on a small team of uebergeeks, more power to ya! But if you work in a corporate environment where half the team is just there to get a paycheck, you're not going to get them to use a tool properly unless using it is easier than not using it.
Grim
(aka Toby)
MCDBA, MCSD, MCP+SB
SELECT * FROM users WHERE clue IS NOT NULL GO
(0 row(s) affected)
-
We had CVS shoved down our throats because that is what our offshore developers were using, and we needed to integrate with what they were doing for us. I guess it was seen as the path of least resistance by those on high for us to change rather than getting the offshore guys to change. I must admit, it is possible to do a lot more in CVS that what were were using before (VSS :sigh:), but it is a bas**rd to learn. I think those folks went out of their way to make it complicated. Cheers,