Comments
Sort by recent activity
Thanks for checking that for me!
I'm afraid I've got another question, but to make up for it, a possible workaround too.
Question: What version of SSMS are you using? [edit - apologies, I've just noticed that you told me the SSMS version in your first post :oops: ]
Potential workaround: There's a hidden keyboard shortcut for Format SQL, "Ctrl+B, Ctrl+L" which was added for backwards compatibility with previous versions of Prompt. You could try that shortcut and see if it works for you. / comments
Thanks for checking that for me!
I'm afraid I've got another question, but to make up for it, a possible workaround too.
Question: What version of SSMS are you using? [edit - apologies, I've just n...
There have been some changes related to key bindings, mostly to improve compatibility with Denali and Visual Studio.
The biggest change is that the key bindings now only apply in the SQL editor scope - i.e. they will only be available when a SQL Query editor tab has the focus. However, I wouldn't expect this to cause any problems, because the commands that the bindings apply to already only work when a SQL query tab is active.
A couple of questions:
1. Is it only the 'Format SQL' command that is affected, or have all the menu commands lost their key bindings?
2. Is there anything interesting in Prompt's logs (from the menu, select SQL Prompt 5 -> Help -> Show Log)? In particular, do any of the log entries mention 'bindings'? / comments
There have been some changes related to key bindings, mostly to improve compatibility with Denali and Visual Studio.
The biggest change is that the key bindings now only apply in the SQL editor sco...
You can download the update directly from http://downloads.red-gate.com/EAP/SQLPromptEAP/SQLPrompt_5.2.0.5.exe
Hope Prompt serves you well in Denali, and please let us know if you encounter any Denali-specific problems! / comments
You can download the update directly from http://downloads.red-gate.com/EAP/SQLPromptEAP/SQLPrompt_5.2.0.5.exe
Hope Prompt serves you well in Denali, and please let us know if you encounter any Den...
Hi Bill,
The latest release candidate of SQL Prompt (5.2.0.5) supports SQL Server Denali CTP3. The release candidate is not available for download from the Red Gate website (that's version 5.1.8.2), but once you have installed the downloaded version, you can use the Check For Updates feature (SQL Prompt 5 -> Help -> Check for Updates...) to get the release candidate.
If you still have problems getting 5.2.0.5 to work in SQL Server Denali, please let me know.
Regards,
Mike Upton / comments
Hi Bill,
The latest release candidate of SQL Prompt (5.2.0.5) supports SQL Server Denali CTP3. The release candidate is not available for download from the Red Gate website (that's version 5.1.8.2)...
Has SQL Server's own intellisense snuck itself back on? Look in the options dialog: in the Text Editor->Transact-SQL page, 'Auto list members' and 'Parameter information' should not be checked, and in Text Editor -> Transact-SQL -> Intellisense, 'Enable IntelliSense' should also be unchecked. / comments
Has SQL Server's own intellisense snuck itself back on? Look in the options dialog: in the Text Editor->Transact-SQL page, 'Auto list members' and 'Parameter information' should not be checked, an...
Thanks for taking the time to report this. I'm looking into it right now :-) / comments
Thanks for taking the time to report this. I'm looking into it right now :-)
I can confirm that this is a problem with existing versions of SQL Prompt running in Visual Studio 2010. It has been assigned issue number SP-3646.
I have identified the root cause of the problem, and the fix should be included in SQL Prompt 5.2.
Regards,
Mike Upton / comments
I can confirm that this is a problem with existing versions of SQL Prompt running in Visual Studio 2010. It has been assigned issue number SP-3646.
I have identified the root cause of the problem, ...
According to the reply to a similar problem posted in the MSDN forums, this can be caused by uninstalling previous versions of Microsoft Visual Studio - apparently it corrupts the .NET framework v2 machine.config file. The original response is at the bottom of the thread here, but to make life easier for you I'll reproduce it:
...If you open up your machine.config file (in %windir%\Microsoft.NET\Framework\v2.0.50727\CONFIG – and in both Framework and Framework64 if you have a 64-bit machine), you’ll probably see an element that looks like this:
<system.serviceModel>
<commonBehaviors>
<endpointBehaviors>
</endpointBehaviors>
<serviceBehaviors>
</serviceBehaviors>
</commonBehaviors>
</system.serviceModel>
If you do see exactly that (probably at the end of the file), then I think we have figured out your problem.
What you need to do is remove this element. So first back-up the machine.config file (save a copy of it to your Desktop or wherever) and then using Notepad, delete that entire <system.serviceModel> element, up to and including </system.serviceModel>. Then save machine.config...
Once you've updated machine.config, you'll definitely need to restart SSMS to see whether that fixes the problem. You may need to restart your machine to persuade the .NET framework to reload the machine.config, although that probably won't be necessary.
Please let us know whether this fixes your problem or not. If it doesn't, we can try to investigate further.
Kind Regards,
Mike Upton / comments
According to the reply to a similar problem posted in the MSDN forums, this can be caused by uninstalling previous versions of Microsoft Visual Studio - apparently it corrupts the .NET framework v2...
Hi Thorsten,
Just wanted to let you know that I haven't forgotten about this. I'm struggling to find anywhere in the current code that could generate this exception (which isn't to say it isn't there somewhere :? ), but it is still on my list of tasks.
Have you tried using Prompt version 5.1.6.35? Does the problem still occur, and if so, is the message in the log exactly the same?
Kind Regards,
Mike / comments
Hi Thorsten,
Just wanted to let you know that I haven't forgotten about this. I'm struggling to find anywhere in the current code that could generate this exception (which isn't to say it isn't the...
Hi Thorsten,
Sorry it's taken so long to get back to you - unfortunately the log message doesn't give me a lot to go on, so this is going to be difficult to track down. I'd be grateful for a little more information from you:
1. What version of SQL Prompt are you using?
2. Are there any noticeable effects on SQL Prompt's behaviour when this message is placed in the log?
Kind Regards,
Mike / comments
Hi Thorsten,
Sorry it's taken so long to get back to you - unfortunately the log message doesn't give me a lot to go on, so this is going to be difficult to track down. I'd be grateful for a little...