We have a visual studio extension we install as part of our product for VS 2010, 2012, and 2013. Our extension is a DDEX extension using the COM API for visual studio extension and registered during the installation through a pkgdef file. Unfortunately, when a user starts SQL Server Management Studio 2012 or later it attempts to load our extension, then decides it shouldn't and reports the ever popular "unable to load extension" error to the user. From turning on logging, we've identified these lines as being about our extension:
<entry><record>1023</record><time>2013/12/16 19:11:43.976</time><type>Information</type><source>VisualStudio</source><description>Entering function CVsPackageInfo::HrInstantiatePackage</description><guid>{6DE8BD69-7008-4A0D-8D5C-634B9BA7008B}</guid></entry><entry><record>1024</record><time>2013/12/16 19:11:43.977</time><type>Warning</type><source>VisualStudio</source><description>Appid denied the loading of package</description><guid>{6DE8BD69-7008-4A0D-8D5C-634B9BA7008B}</guid></entry>So if I'm reading this right, the great irony is that it is loading our assembly, looking at the Package GUID and deciding we're not on the white list for SSMS and not loading us. Which is all fine and good except it throws an error to the user:
How do we prevent SSMS from attempting to load our extension?