PoorMansTSqlFormatter icon indicating copy to clipboard operation
PoorMansTSqlFormatter copied to clipboard

SSMS 18.2 extension 1.6.16 - Disabled menu

Open Progress1 opened this issue 6 years ago • 35 comments

I have disabled actions menu (see picture). It looks that SSMS disable it, but i don't know why. Any experience with this?

image

Progress1 avatar Sep 11 '19 12:09 Progress1

I'm having the same issue on one of my machines. Has anyone figured out why this is happening?

alig114 avatar Sep 16 '19 12:09 alig114

Same behavior after upgrading to SSMS 18.3

Progress1 avatar Sep 24 '19 07:09 Progress1

I'm having the same issue with SSMS 18.2 extension 1.6.16

LuisLlamas avatar Sep 27 '19 17:09 LuisLlamas

i am having the same issue with SSMS 18.2 extension 1.6.16

joydeepkarmakar avatar Sep 28 '19 07:09 joydeepkarmakar

I'm also facing the same issue I'm using SSMS 18.1 extension 1.6.16

srinivaspillalamarri avatar Oct 01 '19 07:10 srinivaspillalamarri

Same on 18.3 extension 1.6.16

AZITWB avatar Oct 01 '19 13:10 AZITWB

Hi all, Same issue with Windows 10 Enterprise 1903, SSMS 18.3. Regards

Racoonator avatar Oct 04 '19 12:10 Racoonator

Installed SSMS 17.6 and now in 18.3 plugin is working :)

AZITWB avatar Oct 05 '19 07:10 AZITWB

Hi,

I installed SSMS 17.9.1 and just after I uninstalled it and now Poor Man Sql works in SSMS 18.3 During the install of 17.9 version, I notice some package relating to VS 2015 was installed.

These packages are still here after the removal of SSMS 17.9

  • Microsoft Visual Studio 2015 Shell (Isolated)
  • Microsoft Visual Studio Tools for Applications 2015
  • Microsoft Visual Studio Tools for Applications 2015 Language Support

I don't know if it's really the reason why now Poor Man works in 18.3, but I can just say the famous "on my computer, it works!"

Racoonator avatar Oct 07 '19 09:10 Racoonator

I believe this is a duplicate of (or at least related to) #234

RichardDavies avatar Oct 09 '19 20:10 RichardDavies

Hi,

I installed SSMS 17.9.1 and just after I uninstalled it and now Poor Man Sql works in SSMS 18.3 During the install of 17.9 version, I notice some package relating to VS 2015 was installed.

These packages are still here after the removal of SSMS 17.9

  • Microsoft Visual Studio 2015 Shell (Isolated)
  • Microsoft Visual Studio Tools for Applications 2015
  • Microsoft Visual Studio Tools for Applications 2015 Language Support

I don't know if it's really the reason why now Poor Man works in 18.3, but I can just say the famous "on my computer, it works!"

I followed the suggest from Racoonator and worked for me too. Thank you.

GelterMacias avatar Oct 09 '19 22:10 GelterMacias

Recommendation from Racoonator worked for me - thanks!

agilotel avatar Nov 02 '19 16:11 agilotel

Microsoft Visual Studio Isolated Shell is the best solution Look into following video I got resolved this https://youtu.be/jcAsmND1C2I

srinivaspillalamarri avatar Nov 03 '19 10:11 srinivaspillalamarri

330Mb installation (just setup) to solve disabled menu :D Is it necessary or it can be solved with some other way? Maybe add-on can be created/compiled without this dependency. Or is MS VS Isolated Shell mandatory to create SSMS add-ons?

Progress1 avatar Nov 04 '19 09:11 Progress1

330Mb installation (just setup) to solve disabled menu :D Is it necessary or it can be solved with some other way? Maybe add-on can be created/compiled without this dependency. Or is MS VS Isolated Shell mandatory to create SSMS add-ons?

I tried with piece by piece installation but I'm not able reach the solution.

But when I checked "ActivityLog.xml" from "AppData\Roaming\Microsoft\AppEnv\15.0" I got one line CreateInstance Failed for package [FormatterPackage]Source: Description: Could not load file assembly Microsoft.VisualStudio.Shell.12.0. By looking at this line I became to know that we need this. That is why tried with VS Shell and I got resolved my issue

srinivaspillalamarri avatar Nov 04 '19 11:11 srinivaspillalamarri

Microsoft SQL Server Management Studio 12.0.2000.8 Microsoft Analysis Services Client Tools 12.0.2000.8 Microsoft Data Access Components (MDAC) 10.0.18362.1 Microsoft MSXML 3.0 4.0 6.0 Microsoft Internet Explorer 9.11.18362.0 Microsoft .NET Framework 4.0.30319.42000 Operating System 6.3.18362

PoorMansTSqlFormatterSSMSPackage.Setup.1.6.16 not working

nhasibuan avatar Nov 20 '19 03:11 nhasibuan

Doesn't work in 18.4 either - I really wish MS would stop changing the bloody dependencies so much...

mika76 avatar Dec 03 '19 08:12 mika76

same issue using 18.4

fhaider2000 avatar Dec 03 '19 14:12 fhaider2000

Microsoft Visual Studio Isolated Shell is the best solution Look into following video I got resolved this https://youtu.be/jcAsmND1C2I

Same issue on a fresh PC Win 10 1803 SSMS 18.4, resolved with installing Visual Studio 2015 Isolated Shell per above.

rishipkothari avatar Dec 13 '19 00:12 rishipkothari

Had this problem on Win10 1903, SSMS 18.4, and PoorSQL 1.6.16 Installing VS 2015 isolated shell fixed it as well, but that seems like a band-aid solution. It's such a great tool...I wish MS would stop pulling the rug out...

m1hammer avatar Jan 19 '20 21:01 m1hammer

I had this issue, installing Isolated shell solved it. I suggest adding a note for this on the download page or making a prerequisite check for it in the PoorSql installer.

wkraft01 avatar Feb 04 '20 21:02 wkraft01

Same issue confirmed on SSMS 18.4/Windows 10 Home 1909/Visual Studio 2019/VS Code/PoorSQL 1.6.16 for SSMS. (Shows 'FormatterPackage' load error as in #234 on first startup.) Installing VS15 Isolated Shell did indeed solve the problem.

BraINstinct0 avatar Feb 13 '20 04:02 BraINstinct0

Microsoft Visual Studio Isolated Shell is the best solution Look into following video I got resolved this https://youtu.be/jcAsmND1C2I

Thank you, the problem solved.

https://aka.ms/VS2015/IsoShell/en-US

image

kjo1 avatar Oct 25 '20 22:10 kjo1

I encountered this with SSMS 18.6. This is the solution I found.

Edit ssms.exe.config C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE

In <assemblyBinding> Add

<dependentAssembly> <assemblyIdentity name="Microsoft.VisualStudio.Shell.12.0" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/> <bindingRedirect oldVersion="2.0.0.0-15.0.0.0" newVersion="15.0.0.0"/> </dependentAssembly>

EltonInAtlanta avatar Nov 17 '20 16:11 EltonInAtlanta

I encountered this with SSMS 18.6. This is the solution I found. Edit ssms.exe.config ...

Nice solution!

Progress1 avatar Nov 18 '20 07:11 Progress1

Work for me, too. Thanks!

r14958 avatar Dec 28 '20 21:12 r14958

I encountered this with SSMS 18.6. This is the solution I found.

Edit ssms.exe.config

This was the solution for me as well. Thanks!

ricky-small avatar Jan 26 '21 23:01 ricky-small

I encountered this with SSMS 18.6. This is the solution I found.

Edit ssms.exe.config C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE

In <assemblyBinding> Add

<dependentAssembly> <assemblyIdentity name="Microsoft.VisualStudio.Shell.12.0" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/> <bindingRedirect oldVersion="2.0.0.0-15.0.0.0" newVersion="15.0.0.0"/> </dependentAssembly>

Worked for me too! Noting, when I tried installing isolated shell that failed. This is a much simpler solution. Nice work!

GraemeJones104 avatar Feb 17 '21 07:02 GraemeJones104

This worked for me as well for v18.9.1

surendra37 avatar May 19 '21 15:05 surendra37

Was attempting the Isolated Shell solution per the top Google result, but that installer wanted me to uninstall the Visual C++ 2015 Redistributable (x86 and x64) to continue.

I went to Apps/Features and clicked "Modify" on the x86 version to see my options before potentially causing more problems. I clicked the "Repair" button in the wizard and it quickly finished. Opened up SSMS and options are actually available now!

I was honestly shocked... I think that's the first time a "Repair" button has actually fixed something for me. 🤣

alexbousquet avatar Jun 07 '21 15:06 alexbousquet