Microsoft Code Destroyer

[PcTek9]

Microsoft's programming environments for languages can be very expensive into the thousands. One of the tools on their expensive software development suites called "sourceSafe" is actually anything but safe.

http://www.highprogrammer.com/alan/windev/sourcesafe.html

On a project I am designing I had the unfortunate experience of trusting microsoft to lose all my data.

Microsoft you may have noticed that by googling there are tons of websites about how unreliable your 'sourceSafe' is, that it deletes code at random, is completely unreliable, etc. etc. It should be listed as a public menace.

I lost from 6/17/2010 to 6/10/2010, in writing source code, but then I ran your database recovery tool, which happily announced nothing is amiss, unfortunately, I am now at 6/8/2010.

 

[iptech]

Wow that's quite shocking. Given the millions of lines of code that Microsoft must handle with their own program development, I wonder if they use it themselves?

 

[MrUnknown]

Switch to Git or at least subversion

 

[PcTek9]

Microsoft does not even use it themselves.

 

[usacvlr]

A number of years ago I was a software engineer with a large company. We used sourcesafe for everything. I absolutely loved it. No more accidentally overwriting someone else's work on the fileserver. The ability to check in and out code modules was a whole new experience at the time. The product may have declined since then as that was back in around 2001.

Microsoft's programming environments for languages can be very expensive into the thousands. One of the tools on their expensive software development suites called "sourceSafe" is actually anything but safe.

http://www.highprogrammer.com/alan/windev/sourcesafe.html

On a project I am designing I had the unfortunate experience of trusting microsoft to lose all my data.

Microsoft you may have noticed that by googling there are tons of websites about how unreliable your 'sourceSafe' is, that it deletes code at random, is completely unreliable, etc. etc. It should be listed as a public menace.

I lost from 6/17/2010 to 6/10/2010, in writing source code, but then I ran your database recovery tool, which happily announced nothing is amiss, unfortunately, I am now at 6/8/2010.

 

[PcTek9]

Well, I loved it at first, but I checked in the code 10 times at least that day, and it acted like it was fine, the code looked fine. the changes were there... but then... then... it got me... It was so mysterious... It looked like what happened was that it lost network connectivity, and decided to open it's on database on the local machine with bubble running.

Since I had no idea it lost network connectivity to the server, and no idea it had opened it's own little world for saving the data locally, when the machine was powered off the bubble burst, and everything was back to a 'new' xp environment with all code lost...

Maybe I will use svn in the future, i'd rather finish the project and just worry about versioning control later. I never went back and checked features I had fixed. I assumed they'd stay fixed. Every day I'd save and it would delete... LOL.

In a way I was about like a gardener planting watermelon seeds, and after getting to the end of a long row, I turn around to see a buzzard is a few steps behind me, and has eaten every seed.

Very frustrated and disappointed.

I usually operate on the KISS principle. So it was very shocking to myself to realize I had allowed unecessary obfuscation to occurr for a simple need which allowed chaos to enter the picture. I'm usually not like that.