Neither .sqlsuo nor .ssmssln will upon attempted "open" in SS Management Studio produce desired result

Question

0.00/5 (No votes)

See more:

Can anybody confirm this behavior or provide a clue as to how a remedy might be obtained:

Attempting to use the interface to get all the files, saved as a specific solution file, to open in there so I can go to work again; gets me a blank project with none of the contents reopening.

Binary editor look at the bigger of the two reveals all filenames intact, paths, etc.

Perhaps a windows update reefed my installation?

Posted 12-Dec-11 7:19am

RedDk

Add a Solution

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)

RedDk · Accepted Answer · 2011-12-15T07:52:00

SOLUTION TO PROBLEM:

More of an observation than a fix because the issue is still with ssmse2k8 and is, in my humble opinion, bad behavior.

When saving a .ssmssln and .sqlsuo the object is to preserve the contents of the browser. IE: all your open .sql scripts where you're actively engaging the database to which you're connected. And this is done by making sure the connection is chosen in the (left) panel "Object Explorer". When one connection is present, the top level one; something along the lines of "computer\instance (SQL Server 10.0.5500 - computer\username)". Next to the "can" with the white/green arrow-circle icon.

This HAS TO BE HIGHLIGHTED when you make your save. And you'll be saving both of the "solution" files.

Now for the content. The open stuff, generally .sql scripts but more officially anything that'll open in the browser, has got to be saved individually as whatever file types they happen to be. I put them in the same directory as the .ssmssln and .sqlsuo but unofficially they could probably be preserved in a sub directory too.

With both the solution and the files enumerated in the solution itself (.xml ... whatever) intact and now saved, you're ready to make the next move.

And that's to HIT THE DISCONNECT ICON IN THE OBJECT BROWSER !!!

Can't emphasize that any more than scream it in capitals.

Once the database is DISCONNECTED ... you can walk away from the interface by closing anything that will close.

THAT procedure should preserve the contents of the solution and make it all available during a quick and efficient reopening at the next ssmse2k8 session.