|
Look this:
http://www.usenix.org/events/usenix-win2000/invitedtalks/lucovsky_html/sld024.htm
Rodrigo Strauss
|
|
|
|
|
|
I heard a rumour a while back that MS is working on a brand new tool.
I gather that VSS was a bought-in tool initially. And it's not really changed in ages.
Kevin
|
|
|
|
|
AFAIK, the initial versions of SourceSafe were made by this guy[^], owner of a small company named "One Tree Software".
Kant wrote:
Actually she replied back to me "You shouldn't fix the bug. You should kill it"
|
|
|
|
|
Interesting. I'd heard that rumour but that's the first time I've seen it confirmed.
Did you know the predecessor product to SourceSafe (Microsoft Delta) was also bought in?
Anna ![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
Homepage | My life in tears
"Be yourself - not what others think you should be"
- Marcia Graesch
"Anna's just a sexy-looking lesbian tart"
- A friend, trying to wind me up. It didn't work.
Trouble with resource IDs? Try the Resource ID Organiser Visual C++ Add-In
|
|
|
|
|
Anna-Jayne Metcalfe wrote:
Interesting. I'd heard that rumour but that's the first time I've seen it confirmed.
Did you know the predecessor product to SourceSafe (Microsoft Delta) was also bought in?
OMG, who takes these decisions, anyway?
Kant wrote:
Actually she replied back to me "You shouldn't fix the bug. You should kill it"
|
|
|
|
|
Calling the Microsoft Visual Sourcesafe a source control tool is similiar to calling a notepad an "Integrated Source Code Editor".
VSS is rather comparable to a simple backup system than a source control utility. It is a very buggy, slow and unreliable backup system at that, and nobody's sources are safe in VSS database as it get's corrupted regularly and exposed for damage.
The worst of all is that it's not a real client-server architecture. Instead, each VSS "client" application is accessing the database on its own (via network share in a typical setup). That leaves the database out in the open and it can be wiped out using file manager from any unit accessing the database. If any of your machines will get infected with a virus it can destroy the database with ease, or worse it could actually alter the code in the database at will, without anybody noticing.
It also makes an interesting observation that there are no advances in the source control field from the Microsof's side. With all that dot net push and with talking about productivity, security and all VSS is still as buggy and unsecure as back in VS6.0 times.
<center> </center>
|
|
|
|
|
What other solution do you propose?
This software is very good!
|
|
|
|
|
There are *plenty* of alternatives. Some good, some bad. A few I can think of off the top of my head:
CVS
PVCS
ClearCase
It seems that from what's been posted here, VSS works fine for small projects and small numbers of programmers, but scales very poorly. I am somewhat surprised that MS doesn't offer a high-end version of VSS for serious programmers.
"When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
|
|
|
|
|
Unless you really hate yourself I wouldn't consider PVCS.
We use that at the moment and it actually makes SourceSafe look good.
It provides every exotic feature that you can think of, but it fails do the basic things correctly. When you do a fetch it doesn't check if you already have the current version of the file. So if you need only to update 2 files in a huge project you have to upload and rebuild the whole thing.
Also, only half works over a WAN.
Also, very buggy unintuitive client SW and just try and get them to fix any of their bugs.
|
|
|
|
|
Seconded. I evaluated PCVS (one of the other devs was very enthusiastic about it) and couldn't believe how counter-intuitive it was.
Stability notwithstanding, when a VSS admin (since 1996, scarily) doesn't feel confident using a souce code control product without going on a training course it may just be a little counter-intuitive...
Anna
Homepage | My life in tears
"Be yourself - not what others think you should be"
- Marcia Graesch
"Anna's just a sexy-looking lesbian tart"
- A friend, trying to wind me up. It didn't work.
Trouble with resource IDs? Try the Resource ID Organiser Visual C++ Add-In
|
|
|
|
|
Have you ever had any problem with a CVS server ?
If you had, you 'd never talk about it as a better alternative to VSS. It have the same (or about the same) problems... Thanks to some good "CVS clients plugin" for eclipse (I used it only on Java projects, VSS was used for any .net / C++ projects I ever worked on), we've messed up the files in the CVS repositroy directory and loosed almost a week of work (Yes, perhaps planning a backup once a week was not what you could have called secured, but...)
As far as I have seen, CVS (and obvioulsy PCVS which is even more difficult to use, lacking of any good tools) is not better than VSS, it's just full of differents design-mistakes. And I do appreciate the default behavior of VSS that requires you to check BEFORE doing any modification in your source code.
My true meaning is not to make use VSS or CVS or any other piece of software : that depends on your dev environment. But NO, CVS is not better than VSS, just different. And, in my opinoion, certainly not to better to be used on wide projects. VSS and CVS are good to use on 1 to 10 (perhaps 20...) peoples projects.
Michael CARBENAY
|
|
|
|
|
I agree with you, I have never seen such a piece of "  sh*tty " software.
Tomas
|
|
|
|
|
Well, maybe a bit of an overstatement, but none of the ones I've seen are convincing.
We use SourceSafe and are looking at CVS, but aren't entirely happy with either. SourceSafe doesn't handle Unicode text well, particularly UTF-8, and CVS - don't start me! I could wax lyrical on how unpleasant it and WinCVS are in usability terms, but our key objection is its default handling of binary files - there's nothing to stop two (or more) people developing different versions of the same file which then can't be merged.
Although there seem to be various hacky configuration options which might mitigate this a bit (we're still investigating these), surely we're not the only developers who have to deal with a mixture of ANSI, UTF-8 and binary files and expect sensible default handling of all three?
Gavin Greig
"Haw, you're no deid," girned Charon. "Get aff ma boat or ah'll report ye."
Matthew Fitt - The Hoose O Haivers: The Twelve Trauchles O Heracles.
|
|
|
|
|
Rational Clearcase - you can check in ANYTHING to it. It does not care.
We put documents, source files, bitmaps, resource files, etc. in five different written languages into ClearCase - it all seems to work just fine.
It has good merging, and developers can work independently in different branches on the same code base, and then merge together at the end. Merging can be a bit difficult if the sources diverge greatly, but for simple simultaneous enhancements and bug fixing, it is great.
I just mention it because everyone here seems to only talk about SS and CVS, I did not see any mention of ClearCase.
You can drive it from the command line or from its COM interface.
It integrates with Visual Studio IDE and the Windows Explorer.
C++/MFC/InstallShield since 1993
|
|
|
|
|
just to say cc is not ideal too (surely price)
the biggest problem for me is mentioned msdev integration (not all options comparing to other access) and terrible refresh problems using it into dynamic view ('source was changed outside editor' messages without reason or 'posponed' refreshes (after build end you want to run and is asks for build, till run-request never asks, next explicit build often makes nothing)
t!
|
|
|
|
|
 I can't believe anybody can like ClearCase. We had an office party after we got rid of it.
|
|
|
|
|
LOL!
At my new job none of the developers "trust" it. The build manager and pm's are constanly sending us e-mail to get use it.
I have only been there a month and have had to rebuild or drop my view twice due to corruption. I think it is as bad as VSS.
Hey don't worry, I can handle it. I took something. I can see things no one else can see. Why are you dressed like that?
- Jack Burton
|
|
|
|
|
I used ClearCase at my first job, and it was a royal pain to setup and start using it. Once we had it properly configured and figured out how to use the config specs, we could do anything we wanted.
I loved the fact that it was tightly integrated into Explorer and DevStudio, making it much easier for me to use. Local snapshots made builds faster, but if you were limited on disk space, you could just build over the network instead.
Bottom line, I wouldn't want to admin it, but I would love to be using it for CM again.
Jason
|
|
|
|
|
Gavin Greig wrote:
SourceSafe doesn't handle Unicode text well, particularly UTF-8
CVSNT[^] can handle Unicode.
Gavin Greig wrote:
but our key objection is its default handling of binary files - there's nothing to stop two (or more) people developing different versions of the same file which then can't be merged.
True, CVS was specifically designed to always allow working as opposed to preventing work (hence "Concurent" in the name). But there are numerous methods to avoid getting in troubles with non-mergable files. With CVSNT the simplest would be to use the reserved edits, which will prevent accidental work on the same version. Combined with email notification for edit's and watches and with the commit notifications which will provide an ongoing information as the file is worked on and commited it makes a pretty good system to avoid problems with non-mergable files.
<center> </center>
|
|
|
|
|
I couldn't agree more. While VSS suits my needs, I have quite a few wants. One of the biggest problems I've had is the whole disconnected case... if I develop on a laptop, then unhook from the network, I cna only work on what I've checked out (granted, I can work on other files, but it's a work around).
I joined in on an open source project to create a new source safe project, taking some key features from VSS, CSVNT, and Subversion. It was also going to include a bug tracking and task management application... all of which would eventually make up a suite of development tools. Unfortunately, the other two developers I was working with lost interest. If anyone would be interested in working on something like this, let me know. I'm game for a pay-product as well as open source.
-AC
-AC
MCDBA
http://www.aconnell.com
|
|
|
|
|
The only good source control programs that I found are SLM and its successor, Source Depot, but both of them are developed and used internally by Microsoft. Nobody uses SourceSafe.
I just wished that Microsoft releases those to external parties. It just has every feature you can imagine and merging capabilities are awesome. Absolute automation and ease--Every checkin is automatically verified and backed out if there is a problem. But then it has to be because it has to handle the Windows source trees which is about a terabyte in size.
Thanks,
Wes
|
|
|
|
|
Where the hell is info on SourceDepot?
I have just been googling for it, and all I see are some hints that it might be by Perforce, and was used to replace the older home grown version control system that the original NT programmers used.
¡El diablo está en mis pantalones! ¡Mire, mire!
Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)!
|
|
|
|
|
No, CVS is the de facto standard for any company doing serious development work. Try doing multi-platform development with VSS. Or try having Ant run automated builds with VSS. CVS is the best version control out there; it's had a long history; it is open source and it works very well with open source. If your company is using anything other than CVS, you need to convince them to switch over to CVS.
cvs -q commit my/2.cents
Ron
|
|
|
|
|
CVS???
I have worked with it and it's terrible!
What's happen when 300 programmer work on the same application???
Go and merge?
The right way is to use VSS.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
