|
Yes, the standalone UI is so badly written that it is a waste of time, but the main problem with PVCS is that it was never designed to work over a WAN. 
|
|
|
|
|
Yeah, but at least they have a web interface - so it's not terrible.
Sometimes I feel like I'm a USB printer in a parallel universe.
|
|
|
|
|
I don't know if I am lazy or what, but as long as the tool that I am using does it's job properly, I stick with it.
Why spend precious time learning a new, maybe better tool ?
I have learned to rely on vss and I am perfectly happy with it.
|
|
|
|
|
VSS stops "working" when you:
1) Put together an ad-hoc team.
2) Need/want to share your code with non-contributors.
3) Need/want to publish your code.
4) Branch.
CodeProject is actually the poster child for the Subversion mission. Having authors copy and paste code into HTML documents rather than just linking to the source is nutty, as well as low-tech. With subversion, they can just be gracefully linked together using ModSVN on Apache.
|
|
|
|
|
|
Let me guess - you have a very small amount of people on your development team?
What I've heard is that it works great if you have a small number of people, but scales very poorly.
Sometimes I feel like I'm a USB printer in a parallel universe.
|
|
|
|
|
I primarily use SourceSafe too, simply because it works out of the box, integrates with Visual Studio, and works ok. However, it has many weaknesses that other systems handle better:
- poor scalability - does not scale well in terms of database size
- poor network support - does not work across slow connections
- single platform - only MS
- no integration with issue tracking software
- no support for linking a batch of changes together, or atomic commits
- tendency towards database becoming corrupted
- limited to the built-in diff tool
- poor support for multiple-checkouts
Sometimes you do not know what you are missing until you try it. I am keen to try Subversion; it sounds like it has great potential.
|
|
|
|
|
Steven Campbell wrote:
limited to the built-in diff tool
I agree with all your points except this one. The diff tool is no worse than WinDiff (but yes they both need improvement IMO). However, there's nothing stopping you from checking out, etc. the files and use your own diff tool.
Steven Campbell wrote:
Sometimes you do not know what you are missing until you try it. I am keen to try Subversion; it sounds like it has great potential.
Ain't it the truth. I might have a look a Subversion too for home-based projects.
Jeremy Falcon
|
|
|
|
|
Hi,
Seems like we should be able to enter more than one response.
Currently I'm using both CVS and Vault depending on which project I'm working on. For some projects I'm using CVS and for other projects I'm using Vault.
Just my two cents,
Michael
Michael Kennedy
Partner, Software Engineer
United Binary, LLC [^]
Index of my code project articles
|
|
|
|
|
|
Hi,
Anonymous wrote:
Why?
Because I am using CVS for my company's projects. Many of these projects go back for years. Switching to Vault would loss all of that history. Plus I am only evaluating Vault as a possible alternative to what we currently use.
But I like Vault better than CVS for a couple of reasons. Plus, Vault is free for single user use. So it makes it perfect for projects that are just my personal projects. For example, my code project articles / code are in my Vault repository.
Some day we may decide to switch our company's projects to Vault, but currently we're sticking with CVS.
That's why I use both CVS and Vault.
Regards,
Michael
Michael Kennedy
Partner, Software Engineer
United Binary, LLC [^]
Index of my code project articles
|
|
|
|
|
Good point:
I also use different SourceControl: at home Subversion, because I need to access my home projects at work through http. At work we use vss because it has beeen working more or less for the last 3 years.
Mathias
|
|
|
|
|
Hi,
Yeah, those are definitely good reasons. In my case both Vault and CVS have good internet accessibility, but that is definitely something to consider. I imagine many people have different version control systems at work and at home.
I especially would expect consultants to use many different version control systems. If you get hired onto a project that is already in progress and in source control there would a strong case to keep whatever system it's in. Then the next project could be the same scenario with a different client and different source control system.
Take care,
Michael
Michael Kennedy
Partner, Software Engineer
United Binary, LLC [^]
Index of my code project articles
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
