Comments
4 comments
-
I'm sorry that you have encountered this problem.
I have spoken to the development team and they think that it may be caused by one of the experimental features which is available in the SQL Prompt Labs. If you are able to do so, can you navigate to the following directory:
C:\Program Files (x86)\Red Gate\SQL Prompt 5\Plugins
and find the file:
RedGate.SQLPrompt.ConnectionColoring.dll
and then rename it, e.g:
RedGate.SQLPrompt.ConnectionColoring.dllold
This will prevent SQL Prompt from being able to load it and therefore should prevent SQL Prompt from loading the code which may be causing your problem.
Please let me know if this workaround makes any difference and I will pass your feedback to the development team. -
Thanks for the response.
Is there any way I can install SQL Prompt into SSMS (SQL Server Management Studio) but NOT as a plug-in to VS 2010?
Rob. -
After install, you can remove SQL Prompt from Visual Studio 2010 by renaming (or deleting) the file %ProgramData%\Microsoft\MSEnvShared\Addins\RedGate.SQLPrompt.VS2010.AddIn
Hope that helps,
Mike -
We believe this problem should now be fixed in SQL Prompt 5.3. Please let us know if it isn't!
Add comment
Please sign in to leave a comment.
This wasn't happening in prior updates.
Any solution to this?