Visual SourceSafe.NET?
-
Thank you George! Much appreciated... I feel scared using a non-MS product were I before used one (VSS to CVS)... Never done this before (well ok I dropped MSN Messenger in favour of Sonork and Trillian but that does not count as MSN Messenger just sucked). Might need to take it slow and ween myself off of VSS... :laugh: regards, Paul Watson Bluegrass Cape Town, South Africa Do you Sonork? I do! 100.9903 Stormfront "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge
It's how I feel, too. We are migrating groups of projects, and we are not migrating VSS history. History is history and we'll mantain it in VSS. We use it rarely. Some links may be useful: CVS for Dummies - Ok, I've read it. Cygwin - You can think about it as if it was a Linux emulator Furor fit laesa saepius patientia
-
Thank you George! Much appreciated... I feel scared using a non-MS product were I before used one (VSS to CVS)... Never done this before (well ok I dropped MSN Messenger in favour of Sonork and Trillian but that does not count as MSN Messenger just sucked). Might need to take it slow and ween myself off of VSS... :laugh: regards, Paul Watson Bluegrass Cape Town, South Africa Do you Sonork? I do! 100.9903 Stormfront "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge
Heh, I must be the only person in the world who doesn't have problems with VSS. :) I tried WinCVS and I wasn't at all impressed. But a lot of that was from the standard "Let's port a Unix app to Windows" problems. Maybe when I will try it again some day. But damn, I really like how VSS hooks into VStudio. Tim Smith Descartes Systems Sciences, Inc.
-
Thank you George! Much appreciated... I feel scared using a non-MS product were I before used one (VSS to CVS)... Never done this before (well ok I dropped MSN Messenger in favour of Sonork and Trillian but that does not count as MSN Messenger just sucked). Might need to take it slow and ween myself off of VSS... :laugh: regards, Paul Watson Bluegrass Cape Town, South Africa Do you Sonork? I do! 100.9903 Stormfront "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge
Just my two cents, for what it's worth... it seems like hooking these types of software into Visual is just a bad idea. I've heard of all kinds of problems with Visual Source Safe. Also, I've used PVCS. If you try to hook it into Visual (it has reasonably good integration), all manners of problems and slowness result. If you use it stand-alone, via command line or its own GUI, it works great. The early bird may get the worm, but the second mouse gets the cheese.
-
Heh, I must be the only person in the world who doesn't have problems with VSS. :) I tried WinCVS and I wasn't at all impressed. But a lot of that was from the standard "Let's port a Unix app to Windows" problems. Maybe when I will try it again some day. But damn, I really like how VSS hooks into VStudio. Tim Smith Descartes Systems Sciences, Inc.
Tim Smith wrote: Heh, I must be the only person in the world who doesn't have problems with VSS. I also use VSS and it works great. :-) Never have had a single problem with it... - Anders Money talks, but all mine ever says is "Goodbye!"
-
Tim Smith wrote: Heh, I must be the only person in the world who doesn't have problems with VSS. I also use VSS and it works great. :-) Never have had a single problem with it... - Anders Money talks, but all mine ever says is "Goodbye!"
We tried it and had endless problem - lost changes, strange "cannot connect to database" type issues, etc. I suspect it was because we needed to "multiple checkouts" active, and VSS seems to heavily favor the "single check out" system. ----------------------------- "I leave no turn un-stoned." - John Simmons, Nov 6 2001 -----------------------------
-
Heh, I must be the only person in the world who doesn't have problems with VSS. :) I tried WinCVS and I wasn't at all impressed. But a lot of that was from the standard "Let's port a Unix app to Windows" problems. Maybe when I will try it again some day. But damn, I really like how VSS hooks into VStudio. Tim Smith Descartes Systems Sciences, Inc.
Tim Smith wrote: I really like how VSS hooks into VStudio. As I said before - there is an SCC interface (aka VSS hooks into VStudio) for CVS: SCC interface, Igloo
-
Thank you George! Much appreciated... I feel scared using a non-MS product were I before used one (VSS to CVS)... Never done this before (well ok I dropped MSN Messenger in favour of Sonork and Trillian but that does not count as MSN Messenger just sucked). Might need to take it slow and ween myself off of VSS... :laugh: regards, Paul Watson Bluegrass Cape Town, South Africa Do you Sonork? I do! 100.9903 Stormfront "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge
Paul Watson wrote: I feel scared using a non-MS product were I before used one I always believed that one has to know their choices. To do that you need to try different things just to have a comparison. ;) BTW: There is one more link worth to follow for CVS installation and guidance. It's kept quite updated and, unlike the official manual, it's not boring: Devguy
-
Heh, I must be the only person in the world who doesn't have problems with VSS. :) I tried WinCVS and I wasn't at all impressed. But a lot of that was from the standard "Let's port a Unix app to Windows" problems. Maybe when I will try it again some day. But damn, I really like how VSS hooks into VStudio. Tim Smith Descartes Systems Sciences, Inc.
Tim Smith wrote: Heh, I must be the only person in the world who doesn't have problems with VSS. I don't have, or had, any problems with VSS either. I simply wanted to see what all the hype is surrounding CVS. Always good to keep my options open and known :) Tim Smith wrote: But damn, I really like how VSS hooks into VStudio I would not consider or use a source system that does not hook into VStudio. Someone else mentioned I should not actually hook CVS into VS but rather use it from it's own GUI or command line. Not a chance! There is no benefit in that, actually a backward step. Bottom line: I was curious about CVS :) regards, Paul Watson Bluegrass Cape Town, South Africa Do you Sonork? I do! 100.9903 Stormfront "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge
-
In beta versions, it came with VSS 6.0c. I'm a great defensor of Microsoft software, but VSS is a big piece of s***. After (another) source code loss with VSS, I'm migrating everything to CVS over SSH. 1. It's free, and you have the sources. If it has annoying bugs or "features", you can fix them. 2. CVS has a branching model much more flexible than VSS. 3. You can work disconnected. 4. It's Client/Server (with SSH) 5. Has encryption and compression (with SSH) 6. The repository is formed by text files. If, for some reason it becomes corrupted, you can manually fix it, or recover some code. 7. The defaults are smarter. It's harder for a dumb programmer to overwrite code by accident. 8. Over VPN it's 3 or 4 times faster than SourceOffSite. And our Win2k server is a dual P3 500Mhz, with 640Mb RAM, very fast SCSI disks. Our Linux server is a AMD K62 400, with 128Mb RAM, ata66 disks. Ok, it's harder to learn & configure, but it's like comparing DBase with SQL Server 2000. Most concepts are very different, and CVS concepts are much more robust, IMHO. If you do not try to emulate VSS with CVS, you even do not need integration in the IDE. I discovered that when you try to do this, your life becomes a hell. Furor fit laesa saepius patientia
It sounds like you use VSS over dialup or the internet a lot. That's probably what caused your corruption. Honestly, I haven't seen a corruption in almost 5 years at any of the sites i've been at (about 10 different companies). That's not to say that VSS doesn't have its problems, it certainly does, but whenever people tell me about their constant corruptions I have to think that it's the way it's being used because my experience doesn't back it up. Any product used in a way that it wasn't designed to be used can have catastrophic failure. -- Where are we going? And why am I in this handbasket?
-
We tried it and had endless problem - lost changes, strange "cannot connect to database" type issues, etc. I suspect it was because we needed to "multiple checkouts" active, and VSS seems to heavily favor the "single check out" system. ----------------------------- "I leave no turn un-stoned." - John Simmons, Nov 6 2001 -----------------------------
I've used multiple checkouts for years with VSS. There are some caveats though, and you need to understand a few things. Lost changes will only occur in a few situations: 1) You are changing files locally without checking it out first, then you checkout the file without getting the most recent version and check it in. 2) You're trying to multiply check out a file that doesn't work well with multiple checkouts (such as the resource.h file) 3) Someone rolls back to a previous version. Those are the only cases where changes can get lost (and this is from nearly 8 years of using VSS (and SS back before MS bought it). All of this boils down to knowing how to use it, ie: user error. Now, there are potential problems with database corruptions. These occur in basically one of three situations: 1) VSS crashes in the middle of a check-in (i've never seen this happen though) 2) You are using a flaky network connection that can drop packets. This is common when dialing in and your connection drops, or when your network has lots of collisions and other problems. 3) Your disk becomes corrupted. If you make sure you are always using a reliable network, and you work on a reliable OS (such as NT/Win2k/XP) then you should never have any real corruption problems. It also helps to run the repair tool at least once a week to clean up minor inconsistencies that can occur from time to time when files are deleted or links changed. So, the rule to having a good VSS experience (for the most part) is: 1) Always use reliable networking 2) Always use a reliable OS 3) Use the multiple checkout feature the way it is supposed to be used, and don't try to work around it. 4) Never try to multiply check out either the .dsp or resource.h file. -- Where are we going? And why am I in this handbasket?