SourceSafe .SSA - BIG PROBLEM

Question

0.00/5 (No votes)

See more:

Hello All,

I have an .ssa file from SourceSafe i need to restore/open but SourceSafe says it might be corrupt and refuses to open it . Does anyone now how I might repair open this file?

Just to clarify, it's not the SourceSafe database files I'm trying to repair, but the backup file (.ssa).

I would be grateful for any help (there's a serious amount of work in this .ssa file).

Thanks all,

Rob

Posted 20-Sep-12 0:14am

talk2robert

Add a Solution

Comments

Sergey Alexandrovich Kryukov 20-Sep-12 12:27pm

That's right. SourceSafe can be a big problem. I warn everyone: don't it it. It is based on some misconceptions, is proprietary (close-source), bulky, non-portable and quite unreliable. Your code asserts are to valuable to put it to risk with such a product.
--SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2012-09-20T06:34:00

Solution 1

Please see my comment to the question.

Now, has at least one version of your code survived somewhere? If so, back up all what you can, take as much of the source code you can save, and run away from SourceSafe as fast as you can, and never come back. Theoretically speaking, if someone insists on using SourceSafe in some company, it could be a sufficient reason to sue such person for malicious activity and sabotage. :-)

Need to know what to do next? Please see this discussion (including my answer):
Revision control systems, which to choose from?[^].

Please see my past answers to related questions:
How can i structured to arrange source code when i create a new solution[^] (in particular, in this one I explain why not VSS),
Needs some words of wisedom to set up and/or use a server[^],
Make an unclickable form[^].

—SA

Posted 20-Sep-12 6:34am

Sergey Alexandrovich Kryukov

Updated 20-Sep-12 13:06pm

v3

Comments

Sergey Alexandrovich Kryukov 20-Sep-12 16:54pm

[OP Commented:]

Hello Sergey,

And thanks for your answer.

We use SourceSafe Server at work and to be honest if something goes wrong I just don't care, because I'm not the person responsible for the server and I will still be payed at the end of the month.

Although I use it at home also (I know how to use it and until didn't want to learn a new system). I do some freelance work and it is this that may be lost. I recently upgraded all my hardware and backed everything up and did a fresh windows 7 install rather than a system backup and so I may have lost some code.

I will be be going across to TortoiseSVN, is it reliable? Does it backup properly?

Thanks again,

Rob

Sergey Alexandrovich Kryukov 20-Sep-12 17:05pm

I would highly recommend Subversion. It's open source, which is important, and it's not only reliable but also extremely light weight. For home use, if you use Windows, I would particular recommend VisualSVN-Server, because it's a build which already contains Apache and Subversion inside and provides the service from one point; you just run the installation -- in addition to Subversion itself, it provides the excellent quality of service. (You don't need HTTPS service at home; SVN also works on its own protocol, but for distributed work it is needed; for me to work along, I use this just for excellent, simple and reliable packaging). For organization, the perfect situation is Linux server and manual configuration, but this is also goes extremely smooth.
If want some more recommendations, I'll gladly answer. By the way, will you accept the answer formally (green button)? -- thanks.
--SA