|
I'm using TortoiseCVS, it's a beautiful GPLed CVS client which integrates into the context menu of the explorer. There's no command line and no emacs syndrom.
And it also works from the file open/save dialogs, even those inside Visual Studio, so I would call it integrated into the ide
---
Author of FileZilla FTP
http://sourceforge.net/projects/filezilla
|
|
|
|
|
Corrupt databases.
No way of running it remotely via simple TCP connections.
No cross-platform support.
Slow.
So bad Microsoft doesn't even use it for most of their projects.
Why on Earth anyone uses Source(Un)Safe is beyond me.
SourceOffsite sucks as well. Start a checkout and you'll quickly see that there's no way to cancel or stop it in progress. Hangs are common.
Blech.
CVS has its own problems, but at least it's free and cross-platform.
|
|
|
|
|
Anonymous wrote:
SourceOffsite sucks as well.
SourceOffsite does have its limitations, I'll grant you that. But when the company I worked for needed to work from two remote locations through a campus (Texas A&M University) firewall, and connect to a preexisting VSS depot -- We were hard pressed to find a better solution that got us up and running. Because everyone was already familiar with VSS from using it in the lab on campus, moving remote and using SourceOffsite saved us time and money.
|
|
|
|
|
I would say it's useful for small projects only.
When we were using it we found the database kept getting corrupted every week or so and that was for max 20 people acessing the database.
|
|
|
|
|
|
Some questions can't be answwered.
Who said that SourceSafe is the defacto standard? Seems to me it's CVS.
|
|
|
|
|
Jim A. Johnson wrote:
Who said that SourceSafe is the defacto standard?
The other survey might suggest just that: Source Code and Version control[^]
Version control is often enforced by the company, so it's not always the best tool that wins the game.
Jim A. Johnson wrote:
Seems to me it's CVS.
CVS is probably the tool of choice whenever one has a choice. It's a de facto standard on Unix, for small, medium and large projects. It's also the most popular over the Internet.
<center> </center>
|
|
|
|
|
George wrote:
The other survey might suggest just that: Source Code and Version control[^]
Ah, I see. Clearly that's a fact I had missed/
I actually enjoyed using VSS when I did, but the last two places I've worked have ignored it; and I thought I was a trend here on CP of CVS being recommneded over VSS.
|
|
|
|
|
Jim A. Johnson wrote:
Who said that SourceSafe is the defacto standard? Seems to me it's CVS.
Not on Windows, hence the clarification in the poll saying "Windows." CVS is seen as the choice of the Unix/Linux crowd. SourceSafe the "choice" of the Windows crowd.
Remember SourceSafe comes with Visual Studio for most Windows developers.
Paul Watson Bluegrass Cape Town, South Africa
Vivek Rajan wrote (about the Matrix):
I assume they are using low colors because they want faster rendering using cheaper hardware... ...Cmon - atleast use 256 colors...
|
|
|
|
|
Paul Watson wrote:
CVS is seen as the choice of the Unix/Linux crowd. SourceSafe the "choice" of the Windows crowd.
Just for the record, the "choice" of the Windows crowd is CVSNT[^] rather than the classic, Unix'y CVS. Those without choice use SourceSafe
<center> </center>
|
|
|
|
|
George wrote:
Those without choice use SourceSafe
Exactly, just what that other chap was saying. That most developers do not have the choice is obvious, hence SourceSafe is the most used on Windows.
Paul Watson Bluegrass Cape Town, South Africa
Vivek Rajan wrote (about the Matrix):
I assume they are using low colors because they want faster rendering using cheaper hardware... ...Cmon - atleast use 256 colors...
|
|
|
|
|
What do you use Paul?
Regards,
Brian Dela
|
|
|
|
|
"My company tells me I have to use it, and therefore I do."
I didn't see that option.
We just got done implememting a LIMS system and there were three of us using it. We all workied on different parts of code. Though the company demanded that if we did any work from home, we log into the company network (and VSS) to access our code.
We just wanted to work on our files at home and update them the next morning. Which in our interest, would have worked.
Anybody else use it cause company policy dictates it?
|
|
|
|