I recently installed VS2019 side-by-side with 2017 (I have not yet moved over to 2019 entirely). Ever since installing VS2019, the Updater/Installer for SQL Prompt Pro only installs the extension into VS2019. The extension is now completely missing from VS2017. Is there a way to force the installer to install into both versions of visual studio? Or is there perhaps something I can do to mark VS2017 as "preferable"?
Comments
10 comments
-
Hi,
Thanks for your post!
SQL Prompt should have installed to all available! It's worth noting this stage that although SQL Prompt appears to have installed into VS2019 for you, this has not been tested by Redgate and is therefore not a supported platform.
You may be able to extract the msi and run the install with the ADDLOCAL=ALL switch as shown in the msiexec command in step 3 from the Install the product section on this page: https://documentation.red-gate.com/xx/installing/installing-from-the-msi-file
Please let us know how you get on! -
Thank you, however this still did not work. It continues to install the extension into VS2019 but not VS2017. My goal is to get it into 2017 and not 19. Is there any way to just get the .vsix extension installer file somehow
-
Hi @pinkfloydx33
I just set up a similar environment and SQL Prompt works as expected in all version of VS and SSMS. Can I just double check, if you open VS17, open a sql file and start to type, do you see SQL Prompt on the top bar?
There is no way to mark VS17 as "preferable" I'm afraid, and usually uninstall and reinstall should bring them back in. -
No it doesn't appear in the top bar. It doesn't appear in the installed extensions list either. It works just fine in SSMS and in VS2019. The problem is I don't really use the latter and want it in 2017.
-
I understand this may not be ideal, but since you don't really need VS2019 can you uninstall it, and then uninstall and reinstall SQL Prompt? Does it hook SQL Prompt to VS2017? You can then install VS2019.
-
The problem with that (and what I experienced originally) is that the next time there is a SQL Prompt update, the extension gets removed from vs2017 and installed into 2019
-
Hi @pinkfloydx33
Can you check if Prompt folder is populated in:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\Extensions\SQLPrompt
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions\SQLPrompt
-
Hi @pinkfloydx33
I'm pleased to let you know this issue is fixed and released. Please uninstall and reinstall the latest version (9.5.4.9799). -
Following is what I have to do so the SQL Prompt will work on both VS 2017 and VS 2019 Enterprise version.
1. Downloaded the update to local machine.
2. Following instruction in (https://documentation.red-gate.com/xx/installing/installing-from-the-msi-file?_ga=2.21199865.371775116.1558531513-1201080811.1550157953&_gac=1.242469558.1558544742.EAIaIQobChMIuaq1x8-v4gIVWgOzAB38wAwjEAAYASAAEgLBUPD_BwE) to extract the package.
3. Uninstall the SQL Prompt (Reboot Machine)
4. Install the SQL Prompt from the step 2's instruction.
** If you try to upgrade directly from the SQL Prompt update. The latest code will either work in in VS2017 or VS2019, but not both. -
Following is what I have to do so the SQL Prompt will work on both VS 2017 and VS 2019 Enterprise version.
1. Downloaded the update to local machine.
2. Following instruction in (https://documentation.red-gate.com/xx/installing/installing-from-the-msi-file?_ga=2.21199865.371775116.1558531513-1201080811.1550157953&_gac=1.242469558.1558544742.EAIaIQobChMIuaq1x8-v4gIVWgOzAB38wAwjEAAYASAAEgLBUPD_BwE) to extract the package.
3. Uninstall the SQL Prompt (Reboot Machine)
4. Install the SQL Prompt from the step 2's instruction.
** If you try to upgrade directly from the SQL Prompt update. The latest code will either work in in VS2017 or VS2019, but not both.
Add comment
Please sign in to leave a comment.