Comments
Sort by recent activity
The tool works fine in SSMS. Is there a way to disable SQL Prompt integration in Visual Studio while keeping it in SSMS? / comments
The tool works fine in SSMS. Is there a way to disable SQL Prompt integration in Visual Studio while keeping it in SSMS?
I just upgraded from v3.1 to v3.5 and I get this error, too. Here are the steps to reproduce it.
1) Make sure SQLPrompt is enabled.
2) In Visual Studio, Open an existing test project or create a new one.
3) Add a new Database Unit Test. You should see the designer with a generic unit test name in the drop down like "DatabaseUnitTest1". The main body of the window will be gray with a hyperlink that says "Click Here to Create" referring to a T-SQL test script.
4) Click the hyperlink to create the test script.
Results: As soon as the T-SQL editor gets the focus, the exception pops up. It won't go away no matter how many times you click Continue. The only way to stop it is to open another application that uses SQL Prompt such as SSMS, go to the SQL Prompt menu and click Disable Sql Prompt. / comments
I just upgraded from v3.1 to v3.5 and I get this error, too. Here are the steps to reproduce it.
1) Make sure SQLPrompt is enabled.
2) In Visual Studio, Open an existing test project or create a n...