Options
Visual Studio integration broken after update; again.
Dave Pendleton
Posts: 104 Bronze 3
in SQL Prompt
As is usual, SQL Prompt integration with Visual Studio is broken after the most recent update.
SQL Prompt appears as installed in the Extensions and Updates dialog.
There is no SQL Prompt menu item.
Keyboard commands do not work.
The SQL Prompt version is 10.8.8.13383
The Visual Studio version is 15.9.17, although this has been happening to me for at least a year, so the version appears to have little to do with it.
The only way to remedy this is to uninstall and reinstall SQL Prompt. If this is in fact the only solution, then please publish that as a requirement and stop offering updates from the Visual Studio UI.
SQL Prompt appears as installed in the Extensions and Updates dialog.
There is no SQL Prompt menu item.
Keyboard commands do not work.
The SQL Prompt version is 10.8.8.13383
The Visual Studio version is 15.9.17, although this has been happening to me for at least a year, so the version appears to have little to do with it.
The only way to remedy this is to uninstall and reinstall SQL Prompt. If this is in fact the only solution, then please publish that as a requirement and stop offering updates from the Visual Studio UI.
Tagged:
Answers
Really sorry to hear you are experiencing a repeat of issues regarding the upgrade of Prompt and how it's interacting with Visual Studio. I've looked into some trending here in our system and unfortunately there doesn't appear to be a lot of reports for this across the base, however this is clearly something that does occur.
I'll ensure this feedback is passed over to the developers so that they can review it and better understand the experiences our customer are seeing.
Great to know that you have a solution to keep things working, but appreciate the workaround is a pain with having to uninstall and reinstall the product.
Karl Boldy | Redgate Software
Have you visited our Help Center?
Downloading the SQLPrompt installer and manually updating SQL Prompt to 10.0.8.13382 appeared to have resolved the problem.