search

TaoK / PoorMansTSqlFormatter

A small free .Net and JS library (with demo UI, command-line bulk formatter, SSMS/VS add-in, notepad++ plugin, winmerge plugin, and demo webpage) for reformatting and coloring T-SQL code to the user's preferences.
http://www.architectshack.com/PoorMansTSqlFormatter.ashx
GNU Affero General Public License v3.0
969 stars 268 forks source link

SSMS 18.2 extension 1.6.16 - Disabled menu #244

Closed Progress1 closed 11 months ago

Progress1 commented 5 years ago

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

image

alig114 commented 5 years ago

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

Progress1 commented 5 years ago

Same behavior after upgrading to SSMS 18.3

LuisLlamas commented 5 years ago

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

joydeepkarmakar commented 5 years ago

i am having the same issue with SSMS 18.2 extension 1.6.16

srinivaspillalamarri commented 5 years ago

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

AZITWB commented 5 years ago

Same on 18.3 extension 1.6.16

Racoonator commented 5 years ago

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

AZITWB commented 5 years ago

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

Racoonator commented 5 years ago

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

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!"

RichardDavies commented 5 years ago

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

GelterMacias commented 5 years ago

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.

agilotel commented 5 years ago

Recommendation from Racoonator worked for me - thanks!

srinivaspillalamarri commented 5 years ago

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

Progress1 commented 5 years ago

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?

srinivaspillalamarri commented 5 years ago

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

nhasibuan commented 5 years ago

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

mika76 commented 4 years ago

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

fhaider2000 commented 4 years ago

same issue using 18.4

rishipkothari commented 4 years ago

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.

m1hammer commented 4 years ago

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...

wkraft01 commented 4 years ago

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.

BraINstinct0 commented 4 years ago

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.

kjo1 commented 4 years ago

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

EltonInAtlanta commented 4 years ago

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>

Progress1 commented 4 years ago

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

Nice solution!

r14958 commented 3 years ago

Work for me, too. Thanks!

ricky-small commented 3 years ago

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!

GraemeJones104 commented 3 years ago

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!

surendra37 commented 3 years ago

This worked for me as well for v18.9.1

alexbousquet commented 3 years ago

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. 🤣

DjJazzyJeffTN commented 3 years ago

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

This guy (@srinivaspillalamarri) nailed it! Good video and thanks for the post.

heerten commented 3 years ago

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>

Quick and easy fix. Remeber to edit the file in administrator mode, otherwise you can't save it ;-) This solved the problem for me, I have SSMS 18.10 installed and now TSQL formatter works like a charm as is already did in Notepad++. Thanks a lot!

berkcinazz commented 3 years ago

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

This also worked for me. Thx a lot.

Lalo11r commented 2 years ago

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>

This worked for me as well, thxs!!

khansadi commented 2 years ago

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>

Awesome find!!