ssms-executor icon indicating copy to clipboard operation
ssms-executor copied to clipboard

SQL Server Management Studio not installed.

Open manngo opened this issue 2 years ago • 7 comments

Some of my remote students are getting this message when trying to install SSMSExecutor on their computer. They all have SSMS 19 installed so that’s obviously not right.

What does this message mean and is there a way around it?

manngo avatar Feb 20 '23 23:02 manngo

Hi @manngo, the installer needs to know where SSMS is installed. So it checks the registry key Computer\HKEY_CURRENT_USER\Software\Microsoft\SQL Server Management Studio\<internal version>_config\InstallDir.

For SSMS 2019 (v18) the registry key should be Computer\HKEY_CURRENT_USER\Software\Microsoft\SQL Server Management Studio\18.0_IsoShell_Config\InstallDir.

Microsoft changed the SSMS naming and it is confusing. When you say SSMS 19, do you mean SSMS 2019 (v18) or SSMS v19.

Can you check with your students witch exact version of SSMS do they have installed (Help > About). And what is stored in the registry key above.

The extension currently does not support SSMS v19 and SQL Server 2022. I am planning to upgrade it soon.

devvcat avatar Feb 21 '23 07:02 devvcat

I mean SSMS v19. I know about the versioning confusion here, and also that the call it version 15 in the vssettings XML file, just in case it wasn’t confusing enough.

As far as I am aware they’re all using SQL Server Express, the currently available version. Are you saying that the server version also affects its behaviour?

manngo avatar Feb 21 '23 19:02 manngo

SSMS v19 is not yet supported by the extension. Working on it.

Yes, SQL Server also affects the behavior, because the parser that I am using may not be aware for server's new features.

devvcat avatar Feb 22 '23 09:02 devvcat

Is there any progress on getting this to work with v19? Is there something we can bandaid to get this going?

manngo avatar May 18 '23 07:05 manngo

Cloning the repository, building with Visual Studio 2017 and pointing to the SSMS 19 instalation worked for me as a workaround.

FabioTomas avatar May 27 '23 21:05 FabioTomas

Cloning the repository, building with Visual Studio 2017 and pointing to the SSMS 19 instalation worked for me as a workaround.

Is there a chance of your sharing this? I don’t have the tools or experience to do this myself.

Thanks

manngo avatar May 28 '23 09:05 manngo

How am I expected to earn a living without this godsend extension!

ishazel avatar Jun 15 '23 10:06 ishazel