We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
We are currently using SourceSafe (multi user/version control program)and there is some dissatisfaction. I would like to know if anyone have pros or cons for other such software.
This will be cross posted at 8052 and SILabs fora
Erik
This is, I know, not a Keil question, but the results are used with Keil
We are currently using SourceSafe (multi user/version control program)and there is some dissatisfaction.
That must be the understatement of the month. The widely accepted point-of-view appears to be that using VSS is at best marginally less silly than printing the source code on paper and eating it. In other words: anything would be better than VSS. Even a pile of print-outs, as long as it's stored and indexed correctly.
Open-source has CVS (with some drawbacks regarding configuration management and massive multi-user use cases), and SVN (just about perfect). Commercial offers I've used and liked include Perforce (terrific for really large code bases) and MKS Source Integrity (includes well-done configuration tracking).
I once had to restore a system from a set of printouts - after the backups failed!
That was back in the days when taking a complete set of listings - on a lineprinter - and binding them all into a bigt folder was normal practice.
Don't knock it - it worked!
I once developed an optical backup system with ECC-korrected laser-printed bitmaps and read back with a scanner. I think I got about 75kB/page.
It was a fun thing to implement, and an alternative to 360, 1200 or 1440 kB floppies :)
The important thing with paper prints is that they can stand quite high temperatures, where a lot of magnetical material gets destroyed.