SSMS 18.2 extension V1.6.13b does not load 'The 'FormatterPackage' package did not load correctly.' - cannot find the file Microsoft.VisualStudio.Shell.12.0 #234

TaoK · 2019-08-01T14:34:35Z

@RichardDavies and @Lukas31781 have had issues installing the SSMS extension (even latest version 1.6.13b) on SSMS 18.2. The setup completes successfully, but when opening SSMS the error The 'FormatterPackage' package did not load correctly. pops up, and the detail in ActivityLog.xml reports that:

The system cannot find the file specified. System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Shell.12.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. 

The system cannot find the file specified. File name: 'Microsoft.VisualStudio.Shell.12.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'   
at System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly assembly, String name, Boolean throwOnError, Boolean ignoreCase, ObjectHandleOnStack type)   
at System.Reflection.RuntimeAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)   
at System.Activator.CreateInstanceFromInternal(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo)   
at System.AppDomain.CreateInstanceFrom(String assemblyFile, String typeName) 

WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. 

Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

The text was updated successfully, but these errors were encountered:

TaoK · 2019-08-01T14:35:18Z

(from unrelated but similar-looking Issue #227)

TaoK · 2019-08-04T10:58:54Z

My very limited understanding of this issue, based on some other issues I've been working on, is that:

In my latest build environment, "Microsoft.VisualStudio.Shell.12.0" was resolving automatically to version 14.0.0.0, and therefore no longer included some of the types it should have contained, in its original version 12.0.0.0.
The correct fix to this would have been annotating the reference with a version for disambiguation, but in my confusion and following Visual Studio's "include reference" autofix suggestion, I added a reference to Microsoft.VisualStudio.Shell.Framework instead.
As a result, working SSMS support required the existing installation of a relatively recent version of visual studio - 2017, I think.

I think I have this fixed, but cannot test, so will appreciate some feedback shortly - I expect to have a new installer out today.

TaoK · 2019-08-04T16:03:22Z

New installer available: https://github.com/TaoK/PoorMansTSqlFormatter/releases/tag/1.6.16

I wasn't able to reproduce, so I can't be sure, but I believe this should address the error. Please let me know.

Lukas31781 · 2019-08-05T06:27:49Z

For me, I have the same problem, first install msi 1.6.16 and get the same information as in version 1.6.13b, the second time I uninstall and install without any changes.

WyattBest · 2019-08-08T20:22:02Z

I still experience this issue with 1.6.16, unfortunately.

Recent, clean install of Windows 10 64-bit 1903, SSMS 18.2, .Net 3.5 and 2.0 installed on-demand by another application that required them. I don't have Visual Studio installed at all.

RichardDavies · 2019-08-12T23:08:11Z

I'm still getting the same error as well with 1.6.16.

KonstantinSat · 2019-08-14T06:44:49Z

Same for me

shaggygi · 2019-08-26T11:01:27Z

Same for me this morning

MessiDaGod · 2019-08-26T17:21:58Z

Mine installed but the links under tools are greyed out

bradfordgreene · 2019-08-27T15:19:48Z

Same issue. PoorSQL options are greyed out. I uninstalled and reinstalled as well. The VS2017 installation is working.

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

federeeko · 2019-08-30T08:43:24Z

PoorSQL options are greyed out

SQL Server Management Studio 15.0.18131.0
Microsoft Analysis Services Client Tools 15.0.1347.0
Microsoft Data Access Components (MDAC) 10.0.17134.1
Microsoft MSXML 3.0 6.0
Microsoft Internet Explorer 9.11.17134.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 10.0.17134

alexiscomte · 2019-09-10T08:34:19Z

Hi I have the same issue

SQL Server Management Studio 15.0.18142.0
Outils clients Microsoft Analysis Services 15.0.1389.0
Microsoft Data Access Components (MDAC) 10.0.18362.1
Microsoft MSXML 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 9.11.18362.0
Microsoft .NET Framework 4.0.30319.42000
Système d'exploitation 10.0.18362

alexiscomte · 2019-09-10T08:36:11Z

I used the 1.6.16 installler

WyattBest · 2019-09-13T20:58:21Z

Installing SSMS 17.9 alongside 18.2 causes the extension to work! Going to do that until it's fixed; I missed this tool so much.

PETERHUP · 2019-09-25T00:00:10Z

Installing SSMS 17.9.1 made the formatting tool work for me too in SSMS, must be a missing library or something. Love the tool too, hope this gets fixed.

RichardDavies · 2019-10-09T20:39:29Z

Any update on when this will be fixed? (It shouldn't be marked resolved as there are still many people reporting this issue.)

drenkelfuss · 2019-10-22T11:12:30Z

The issue still exists. Clean Windows Install /w SSMS 18.3 and PoorMansSQL Installer 1.6.16

shmulyeng · 2019-10-29T15:53:00Z

Same issue here. Any update?

aphalon · 2019-11-01T09:21:54Z

There are a lot of dependency problems with the current version of SSMS 18.3.1 and the extension.

In the end I took the projects and re-referenced them against the Nuget versions of their dependencies and upped the .net version to 4.6 and built them and copied them to the X:\Program Files (x86)\PoorMansTSqlFormatterSSMSExtension folder (replace X with your drive letter) and removed the LinqBridge.dll file (seems to come free with the .net install).

Happy to share those DLLs if people want them (https://drive.google.com/open?id=1LI1nlRmlPNg1EkW-B_ydwzAzrHfbJ8m3) - not really an ideal solution but may help.

As a caveat it's had limited testing (under 5 minutes - once it worked a few times and reformatted SQL didn't really do much else) on a single newly built machine and has no guarantee of it working in your environment.

Trallali · 2019-11-02T21:45:17Z

Happy to share those DLLs if people want them

This works for me on a fresh german Win10 + SSMS 18.3.1. Thanks!

tkvw · 2019-11-13T16:10:04Z

@aphalon : can you make a PR? I like to use your solution as well, but randomly downloading dll's from an untrusted source doesn't make me feel comfortable 😄

m1hammer · 2020-01-16T15:01:10Z

Using SSMS 18.4 and Windows 10 v1903 -- I am still experiencing this problem using PoorSQL 1.6.16.
"FormatterPackage' package did not load correctly." and the PoorSQL menu options are disabled.
I have another PC with the same configuration, and it works fine on that unit.

eng1n88r · 2020-01-17T15:52:14Z

Installing VS Isolated Shell solved my issue. I have SSMS 18.4 and PMSF 1.6.16

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

jmoralesv · 2020-03-01T05:26:46Z

Same issue here, using SSMS 18.4, Windows 10 version 1909 and Visual Studio 2019 version 16.4. The file C:\Users\{my_user_name}\AppData\Roaming\Microsoft\AppEnv\15.0\ActivityLog.xml records this message:

CreateInstance failed for package [FormatterPackage]Source: "mscorlib" Description: Could not load file or assembly "Microsoft.VisualStudio.Shell.12.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" or one of its dependencies. The system cannot find the file specified.
System.IO.FileNotFoundException: Could not load file or assembly "Microsoft.VisualStudio.Shell.12.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" or one of its dependencies. The system cannot find the file specified.
File name: "Microsoft.VisualStudio.Shell.12.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
   at System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly assembly, String name, Boolean throwOnError, Boolean ignoreCase, ObjectHandleOnStack type)
   at System.Reflection.RuntimeAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
   at System.Activator.CreateInstanceFromInternal(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo)
   at System.AppDomain.CreateInstanceFrom(String assemblyFile, String typeName)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

When SSMS finishes loading, the two options for Poor SQL are grayed out under the Tools menu.

Will there be a new version that solves this in SSMS 18.4?

KonstantinSat · 2020-03-01T07:28:51Z

@jmoralesv
Installing the missing "VS isolated shell" solves the issue:

Installing VS Isolated Shell solved my issue. I have SSMS 18.4 and PMSF 1.6.16

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

obohaciak · 2020-06-09T10:13:11Z

Helped me too. Running SSMS 18.5, PSMF 1.6.16 and VS 16.6.0

@jmoralesv
Installing the missing "VS isolated shell" solves the issue:

WereGoingOcean · 2020-06-29T12:00:12Z

The issue seems to be with a binding redirect missing from SSMS.

If you edit ssms.exe.config (by default at C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE) and add the following line inside the assemblyBinding element the package will load:

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

There's one for shell 9.0, 10.0, and 14.0 just not one for 12.0. I took the above from the visual studio exe.config. This will get cleared and have to be re-done any time you update SSMS.

kjo1 · 2020-08-28T17:20:35Z

The issue seems to be with a binding redirect missing from SSMS.

If you edit ssms.exe.config (by default at C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE) and add the following line inside the assemblyBinding element the package will load:

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

There's one for shell 9.0, 10.0, and 14.0 just not one for 12.0. I took the above from the visual studio exe.config. This will get cleared and have to be re-done any time you update SSMS.

This totally works!

kaisp84 · 2020-11-19T14:14:15Z

I face the same issue on SSMS 18.6. Entries in ActivityLog.xml

<entry>
    <record>120</record>
    <time>2020/11/19 13:54:07.211</time>
    <type>Information</type>
    <source>VisualStudio</source>
    <description>Begin package load [FormatterPackage]</description>
    <guid>{247609B1-2692-47D6-972A-976544685F0E}</guid>
  </entry>
  <entry>
    <record>121</record>
    <time>2020/11/19 13:54:07.373</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>CreateInstance failed for package [FormatterPackage]Source: &apos;mscorlib&apos; Description: Could not load file or assembly &apos;Microsoft.VisualStudio.Shell.12.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a&apos; or one of its dependencies. The system cannot find the file specified.&#x000D;&#x000A;System.IO.FileNotFoundException: Could not load file or assembly &apos;Microsoft.VisualStudio.Shell.12.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a&apos; or one of its dependencies. The system cannot find the file specified.&#x000D;&#x000A;File name: &apos;Microsoft.VisualStudio.Shell.12.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a&apos;&#x000D;&#x000A;   at System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly assembly, String name, Boolean throwOnError, Boolean ignoreCase, ObjectHandleOnStack type)&#x000D;&#x000A;   at System.Reflection.RuntimeAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)&#x000D;&#x000A;   at System.Activator.CreateInstanceFromInternal(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo)&#x000D;&#x000A;   at System.AppDomain.CreateInstanceFrom(String assemblyFile, String typeName)&#x000D;&#x000A;&#x000D;&#x000A;WRN: Assembly binding logging is turned OFF.&#x000D;&#x000A;To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.&#x000D;&#x000A;Note: There is some performance penalty associated with assembly bind failure logging.&#x000D;&#x000A;To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].&#x000D;&#x000A;</description>
    <guid>{247609B1-2692-47D6-972A-976544685F0E}</guid>
    <hr>80004005 - E_FAIL</hr>
    <errorinfo></errorinfo>
  </entry>

jhullparkseed · 2021-03-09T17:10:17Z

I had the same issue and came in to say that adding the binding settings to the SSMS config file (see fix above) worked. Great add in other than the opps in install.

speedy32129 · 2021-03-23T14:57:56Z

Changing the SSMS config worked for me!!!

federeeko · 2021-03-25T08:42:04Z

The issue seems to be with a binding redirect missing from SSMS.

If you edit ssms.exe.config (by default at C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE) and add the following line inside the assemblyBinding element the package will load:

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

There's one for shell 9.0, 10.0, and 14.0 just not one for 12.0. I took the above from the visual studio exe.config. This will get cleared and have to be re-done any time you update SSMS.

Worked like a charm - thx

francesco1119 · 2021-05-07T12:20:20Z

Worked like a charm - thx

What file is the assemblyBinding @federeeko ?

I cannot find it under C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE

jordi00113 · 2021-11-30T19:11:41Z

The issue seems to be with a binding redirect missing from SSMS.

If you edit ssms.exe.config (by default at C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE) and add the following line inside the assemblyBinding element the package will load:

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

There's one for shell 9.0, 10.0, and 14.0 just not one for 12.0. I took the above from the visual studio exe.config. This will get cleared and have to be re-done any time you update SSMS.

Still works on Microsoft SQL Server Management Studio 18 anno 2021

omaracos · 2021-12-28T16:35:55Z

The issue seems to be with a binding redirect missing from SSMS.

If you edit ssms.exe.config (by default at C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE) and add the following line inside the assemblyBinding element the package will load:

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

There's one for shell 9.0, 10.0, and 14.0 just not one for 12.0. I took the above from the visual studio exe.config. This will get cleared and have to be re-done any time you update SSMS.

this Worked! thanks.

sushant047 · 2022-01-29T16:16:54Z

The issue seems to be with a binding redirect missing from SSMS.

If you edit ssms.exe.config (by default at C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE) and add the following line inside the assemblyBinding element the package will load:

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

There's one for shell 9.0, 10.0, and 14.0 just not one for 12.0. I took the above from the visual studio exe.config. This will get cleared and have to be re-done any time you update SSMS.

Awesome! It did work like a charm :) Tried it on SSMS v18.9.2 and OS 10.0.19044

dusfor72 · 2022-02-10T08:43:55Z

The issue seems to be with a binding redirect missing from SSMS.

If you edit ssms.exe.config (by default at C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE) and add the following line inside the assemblyBinding element the package will load:

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

There's one for shell 9.0, 10.0, and 14.0 just not one for 12.0. I took the above from the visual studio exe.config. This will get cleared and have to be re-done any time you update SSMS.

Just had the same problem and can confirm that this fix works! Great community, thanks a lot!

CH-Kev · 2022-03-29T13:54:50Z

Updated to SMSS 18.11.1 this morning.

I edited edit ssms.exe.config, added the dependent assembly entry for Microsoft.VisualStudio.Shell.12.0 like I do after each update. This time it didn't work, there's now a comment block at the top ssms.exe.config:

<!-- *************************************************************************** -->
<!-- ************** NOTE: This is a generated file. Do not modify.************** -->
<!-- ********* Modifications will be overwritten during regeneration. ********** -->
<!-- *************************************************************************** -->

Started ssms after the edit and PoorMansTSqlFormatter was still greyed out. Went back and checked ssms.exe.config and the dependent assembly entry for Microsoft.VisualStudio.Shell.12.0 was no longer there. It would appear that ssms.exe.config is now regenerated at runtime.

Installing VS Isolated Shell as suggested by exbarboss on 1/17/2020. Opened SSMS again and PoorMansTSqlFormatter now works.

Installing VS Isolated Shell solved my issue. I have SSMS 18.4 and PMSF 1.6.16

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

i-snake-z · 2022-03-30T10:43:37Z

Updated to SMSS 18.11.1 this morning.

I edited edit ssms.exe.config, added the dependent assembly entry for Microsoft.VisualStudio.Shell.12.0 like I do after each update. This time it didn't work, there's now a comment block at the top ssms.exe.config:




Started ssms after the edit and PoorMansTSqlFormatter was still greyed out. Went back and checked ssms.exe.config and the dependent assembly entry for Microsoft.VisualStudio.Shell.12.0 was no longer there. It would appear that ssms.exe.config is now regenerated at runtime.

Installing VS Isolated Shell as suggested by exbarboss on 1/17/2020. Opened SSMS again and PoorMansTSqlFormatter now works.

Installing VS Isolated Shell solved my issue. I have SSMS 18.4 and PMSF 1.6.16
https://aka.ms/VS2015/IsoShell/en-US

Thank You very much, instaling VS Isolated shell resolve the problem

jorgesomers · 2022-06-01T02:47:52Z

Hi,

This is not realy a perfect solution - but it took me 5 minutes to solve my problem since I´ve updated my Sql Server to 18.x !

There are a lot of dependency problems with the current version of SSMS 18.3.1 and the extension.

In the end I took the projects and re-referenced them against the Nuget versions of their dependencies and upped the .net version to 4.6 and built them and copied them to the X:\Program Files (x86)\PoorMansTSqlFormatterSSMSExtension folder (replace X with your drive letter) and removed the LinqBridge.dll file (seems to come free with the .net install).

Happy to share those DLLs if people want them (https://drive.google.com/open?id=1LI1nlRmlPNg1EkW-B_ydwzAzrHfbJ8m3) - not really an ideal solution but may help.

As a caveat it's had limited testing (under 5 minutes - once it worked a few times and reformatted SQL didn't really do much else) on a single newly built machine and has no guarantee of it working in your environment.

spike1234 · 2022-06-24T10:12:50Z

Hi,

This is not realy a perfect solution - but it took me 5 minutes to solve my problem since I´ve updated my Sql Server to 18.x !

There are a lot of dependency problems with the current version of SSMS 18.3.1 and the extension.
In the end I took the projects and re-referenced them against the Nuget versions of their dependencies and upped the .net version to 4.6 and built them and copied them to the X:\Program Files (x86)\PoorMansTSqlFormatterSSMSExtension folder (replace X with your drive letter) and removed the LinqBridge.dll file (seems to come free with the .net install).
Happy to share those DLLs if people want them (https://drive.google.com/open?id=1LI1nlRmlPNg1EkW-B_ydwzAzrHfbJ8m3) - not really an ideal solution but may help.
As a caveat it's had limited testing (under 5 minutes - once it worked a few times and reformatted SQL didn't really do much else) on a single newly built machine and has no guarantee of it working in your environment.

After updating to v18.12.1, modifying the .config files stopped working, but those DLL seems to work correctly.
Thanks!

dmks22 · 2022-07-14T04:38:40Z

Thank you

lcichanowicz · 2022-09-27T16:28:31Z

Per @CH-Kev 's recommendation, I too simply installed VS Isolate Shell, and that worked.

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

I got this warning, but everything works fine.

kingswoodfgao · 2022-10-01T23:36:05Z

By looking at the ssms.exe.config, there is no assembly redirect entry for "Microsoft.VisualStudio.Shell.12.0", so added the following assembly redirect fixed my problem:

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

james-poulose · 2023-01-06T19:11:28Z

The issue seems to be with a binding redirect missing from SSMS.

If you edit ssms.exe.config (by default at C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE) and add the following line inside the assemblyBinding element the package will load:

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

There's one for shell 9.0, 10.0, and 14.0 just not one for 12.0. I took the above from the visual studio exe.config. This will get cleared and have to be re-done any time you update SSMS.

As of today, this is still the best fix!

dwillis77 · 2023-06-15T21:42:08Z

Updated to SMSS 18.11.1 this morning.

I edited edit ssms.exe.config, added the dependent assembly entry for Microsoft.VisualStudio.Shell.12.0 like I do after each update. This time it didn't work, there's now a comment block at the top ssms.exe.config:




Started ssms after the edit and PoorMansTSqlFormatter was still greyed out. Went back and checked ssms.exe.config and the dependent assembly entry for Microsoft.VisualStudio.Shell.12.0 was no longer there. It would appear that ssms.exe.config is now regenerated at runtime.

Installing VS Isolated Shell as suggested by exbarboss on 1/17/2020. Opened SSMS again and PoorMansTSqlFormatter now works.

Installing VS Isolated Shell solved my issue. I have SSMS 18.4 and PMSF 1.6.16
https://aka.ms/VS2015/IsoShell/en-US

Strange, I just installed v18.12.1 today and I don't see that block at the top of the config - and making the changes did work for me (I guess we'll see if they stick though...).

FYI this fix also works to get the extension working in SSMS v19 when used in conjunction with the process described here.

TaoK mentioned this issue Aug 1, 2019

SSMS 18.1 extension V1.6.13 does not load 'The 'FormatterPackage' package did not load correctly.' - Assembly Version Mismatches #227

Closed

TaoK added the priority-high label Aug 1, 2019

TaoK added a commit that referenced this issue Aug 4, 2019

Attempt fix SSMS version support issues (2014 & 18): #194, #234

2e9dec3

TaoK added the resolved label Aug 4, 2019

RichardDavies mentioned this issue Oct 9, 2019

SSMS 18.2 extension 1.6.16 - Disabled menu #244

Closed

WyattBest mentioned this issue May 12, 2020

error when opening ssms after install #255

Open

freshwave13 mentioned this issue Mar 31, 2022

Installation Error in SSMS v18.11.1 #281

Open

dwillis77 mentioned this issue Jun 15, 2023

SSMS 19 - Compatibility #283

Open

SSMS 18.2 extension V1.6.13b does not load 'The 'FormatterPackage' package did not load correctly.' - cannot find the file Microsoft.VisualStudio.Shell.12.0 #234

SSMS 18.2 extension V1.6.13b does not load 'The 'FormatterPackage' package did not load correctly.' - cannot find the file Microsoft.VisualStudio.Shell.12.0 #234

Comments

TaoK commented Aug 1, 2019

TaoK commented Aug 1, 2019

TaoK commented Aug 4, 2019 • edited Loading

TaoK commented Aug 4, 2019

Lukas31781 commented Aug 5, 2019

WyattBest commented Aug 8, 2019 • edited Loading

RichardDavies commented Aug 12, 2019

KonstantinSat commented Aug 14, 2019

shaggygi commented Aug 26, 2019

MessiDaGod commented Aug 26, 2019

bradfordgreene commented Aug 27, 2019

federeeko commented Aug 30, 2019 • edited Loading

alexiscomte commented Sep 10, 2019

alexiscomte commented Sep 10, 2019

WyattBest commented Sep 13, 2019

PETERHUP commented Sep 25, 2019

RichardDavies commented Oct 9, 2019

drenkelfuss commented Oct 22, 2019

shmulyeng commented Oct 29, 2019

aphalon commented Nov 1, 2019

Trallali commented Nov 2, 2019 • edited Loading

tkvw commented Nov 13, 2019

m1hammer commented Jan 16, 2020

eng1n88r commented Jan 17, 2020

jmoralesv commented Mar 1, 2020

KonstantinSat commented Mar 1, 2020

obohaciak commented Jun 9, 2020

WereGoingOcean commented Jun 29, 2020

kjo1 commented Aug 28, 2020

kaisp84 commented Nov 19, 2020 • edited Loading

jhullparkseed commented Mar 9, 2021

speedy32129 commented Mar 23, 2021

federeeko commented Mar 25, 2021

francesco1119 commented May 7, 2021 • edited Loading

jordi00113 commented Nov 30, 2021

omaracos commented Dec 28, 2021

sushant047 commented Jan 29, 2022 • edited Loading

dusfor72 commented Feb 10, 2022

CH-Kev commented Mar 29, 2022 • edited Loading

i-snake-z commented Mar 30, 2022

jorgesomers commented Jun 1, 2022

spike1234 commented Jun 24, 2022

dmks22 commented Jul 14, 2022

lcichanowicz commented Sep 27, 2022

kingswoodfgao commented Oct 1, 2022 • edited Loading

james-poulose commented Jan 6, 2023

dwillis77 commented Jun 15, 2023

TaoK commented Aug 4, 2019 •

edited

Loading

WyattBest commented Aug 8, 2019 •

edited

Loading

federeeko commented Aug 30, 2019 •

edited

Loading

Trallali commented Nov 2, 2019 •

edited

Loading

kaisp84 commented Nov 19, 2020 •

edited

Loading

francesco1119 commented May 7, 2021 •

edited

Loading

sushant047 commented Jan 29, 2022 •

edited

Loading

CH-Kev commented Mar 29, 2022 •

edited

Loading

kingswoodfgao commented Oct 1, 2022 •

edited

Loading