Suggestions are not working after Visual Studio updating
Ruslan
Posts: 2 New member
in SQL Prompt
Hello.
I have an issue with SQL Prompt Core suggestions loading after VS Enterprise 2017 update to 15.5.2.
I had the same issue with last update of visual Studio. I had to completely reinstall Visual Studio for suggestions fix. Now I have the same issue after VS update and this bug interrupt my working process again.
I reinstalled VS and SQL Prompt Core extension but suggestions still are not loading. I checked settings and all check boxes are checked.
Please provide me some information about this issue. And how to fix it?
I have an issue with SQL Prompt Core suggestions loading after VS Enterprise 2017 update to 15.5.2.
I had the same issue with last update of visual Studio. I had to completely reinstall Visual Studio for suggestions fix. Now I have the same issue after VS update and this bug interrupt my working process again.
I reinstalled VS and SQL Prompt Core extension but suggestions still are not loading. I checked settings and all check boxes are checked.
Please provide me some information about this issue. And how to fix it?
Tagged:
Best Answer
-
Michael Clark Posts: 123 Silver 4Hi @Ruslan,
I think this issue may be related to these two threads.
https://forum.red-gate.com/discussion/82047/sql-prompt-core-suggestions-for-ssdt-projects#latest
https://forum.red-gate.com/discussion/82094/sql-prompt-core-doesnt-work-in-visual-studio-2017
What version of SQL Prompt Core are you using?
You can find the version in the menu SQL Prompt -> Help -> About SQL Prompt
We changed behaviour in recent releases so that we do not override SSDT autocomplete if you have a SSDT Database Project in your solution. Do you have a SSDT Database Project?
Best wishes,
Michael
Michael Clark
Technical Lead, SQL Monitor
Answers
I don't want the suggestions to come from my SSDT project want them to come from the database that I connected the query window to, but it seams as long as I have an SSDT project open SQL prompt is useless. Or I need to open a separate copy of VS 2017, which is a resource hog, in order to get the suggestions. Why not give the user a choice to disable SQL Prompt in favor of the regular SSDT autocomplete instead of forcing it. One reason I started using VS and SQL prompt was that the regular intellisense rarely worked in SSMS when connecting to our remote servers.
Thanks for joining and for your post.
You can always make suggestions on our SQL Prompt Uservoice page in the link below so that ideas can be considered for future development.
https://redgate.uservoice.com/forums/94413-sql-prompt
Kind regards
Redgate Software