Excel VBA - industrialisation...Part Ten "Enumerating COMAddins"

This post is concerned with looking at COM Addins. The COM Addin is part of the Office Object Model rather than Excel and was part of a Microsoft process to try and unify the different implementations of VBA.

COM Addins can, as the name suggests, be created in any language that supports COM. In the past I have done so in VB6 which was very easy. The move to dot net meant that there was a need for more code to get from the COM world to the CLR. And the process of deploying VB6 based COM Addins in Excel 2013 has been further complicated by Microsoft removing some components needed at run time.

Following on from the earlier posts on enumerations "Enumerating DDE Servers", "Enumerating RTD Servers", "Enumerate Addin references"

As we have seen within the Enumerating RTD Servers post, from a ProgID we can find the actual code that is executed, so that is not shown in the VBA code in this example. And of course, from a GUID of a COM object it's trivially simple to find the code.

To enumerate all of the COMAddins in a particular instance of Excel, follow these steps:

Download the code from github

Create a new Excel workbook with one worksheet.

Save the new workbook as an xlsm format workbook

Enter the VBA editor

Import the module you just downloaded from github

Execute the "EntryPointGetCOMAddinReferences" method and look in the debug window

Global Electronic Trading

Search This Blog

Excel VBA - industrialisation...Part Ten "Enumerating COMAddins"

Comments

Post a Comment