Shiny things that caught my eye
Translate This Page
Translate this page
VSTO Doc Solutions
VSTO Power Tools
Browse by Tags
Tagged Content List
Exposing Events From Non-VSTO Add-in Automation Objects
I posted a while back about exposing an automation object from an add-in that fires events . That post was couched in terms of VSTO add-ins. A customer asked recently how the same technique could be used in a non-VSTO add-in. So, that’s the topic of this post. First, here’s my automation object and...
1 Mar 2009
Exposing Events from Managed Add-in Objects
Following on from my recent posts on exposing add-in objects, here and here , it occurred to me that its sometimes useful to be able to expose events from these objects. Recall that you can expose your add-in through the COMAddIn.Object property in the Office OM, either directly (in a non-VSTO add-in...
13 Oct 2008
COMAddIns Race Condition
You can expose an arbitrary object from your add-in as a kind of extension to the Office host application’s object model. To do this, you set your object as the value of the Object property on the COMAddIn object that represents your add-in in the host’s COMAddIns collection object. You can do this directly...
13 Aug 2008
Why your COMAddIn.Object should derive from StandardOleMarshalObject
In general, it is important that any code in a managed Office add-in should execute on the main UI thread. The reason for this is that there are several components that simply will not work when executed from any other but the main UI thread – examples include calls on WinForms controls, and calls into...
11 Aug 2008
Integrating Doc-level and Add-in Solutions
Everyone knows you can build document-level Office solutions and you can build application-level Office add-ins. Suppose your requirements dictate that you build a solution that uses both techniques – can this be done? First, let’s pause and consider whether this is a good idea in the first place, and...
20 Mar 2008
VSTO Add-ins, COMAddIns and RequestComAddInAutomationService
The COMAddIns property is a collection of COMAddIn objects exposed by Office applications that support COM add-ins. The COMAddIn interface defines a small number of methods/properties, such as the ProgId of the add-in and the Connect state. It also defines an Object property. By default, the value of...
15 Jan 2007
Page 1 of 1 (6 items)
© 2013 Microsoft Corporation.
Privacy & Cookies