Much of what I have read about Esri Add-Ins describe these unique containers of custom ArcGIS Desktop functionality as having behaviours that make deployment, installation and development “easier”. That is, easier than that required by their predecessor – the Classic COM component, which became an essential for Desktop customisation when ArcObjects first hit the scene in the late 90’s.
I have “walked through” numerous help references and tutorials that are based around the Esri Add-In type, but none that I have found articulate the “how” of the Esri Add-In. That is, how can the Add-In type have such new and appealing deployment characteristics ? – There is many a forum posting and support request focused on the intricacies of COM registration and deployment; The first Add-In type , to which we were introduced at Desktop 10.0, utilises ArcObjects libraries; ArcObjects libraries are COM libraries. How then, could the Esri Add-In model employ ArcObjects “COM” libraries, without the need for registration on the underlying operating system?
….And so for an explanation: Continue reading