Comments
Sort by recent activity
I have this as well. Can Red Gate please add some decent default exception handling to SQL Prompt so that bugs / errors like this don't take out Sqlwb.exe? When I had this error SQL Prompt appeared to be in an infinite loop and the exception message box kept reappearing everytime I clicked "Continue". It was not possible to save or "rescue" any of the open scripts. Please take a look at resharper and how it handles exceptions. When an unexpected exception occurs you can tell it not to bother you anymore with error messages. I would rather have Sql Prompt stop working than lose work.
These should be non-negotiable:
(1) SQL Prompt should never take out SqlWb.exe, and
(2) A user should never lose work because of SQL Prompt. / comments
I have this as well. Can Red Gate please add some decent default exception handling to SQL Prompt so that bugs / errors like this don't take out Sqlwb.exe? When I had this error SQL Prompt appeare...
SQL Prompt has become unusable for me as this bug brings down SSMS. In future could you add some default Exception handlers to your SSMS add-ins so that they don't crash the application? R# (an add-in to Visual Studio) offers to send the Exception home and then not bother you anymore. As I cannot risk crashing SSMS at random intervals I've had to disable SQL Prompt till this is fixed. :x / comments
SQL Prompt has become unusable for me as this bug brings down SSMS. In future could you add some default Exception handlers to your SSMS add-ins so that they don't crash the application? R# (an add...