Trouble with Live Search Maps Add-in for Outlook

Several million of you have downloaded the Live Search Maps Add-in for Outlook which allows integration in Outlook with maps and has some cool functionality around extending your appointment blocks to account for automatically calculated travel time among other things. We have received a large number of support cases that are caused either directly or…


Misha Shneerson : COM Interop: Handling events has side effects

Misha, a Senior Dev on the VSTO team just posted this blog describing why handling events in managed code can be problematic. This is not news to our team, but he provides a good explanation of why it’s problematic. Misha Shneerson : COM Interop: Handling events has side effects If any of what he says…


Form Region Leak in Visual Studio Tools for Office 2008 (v3) Template

I had a case on this a few months ago, but thought more folks might run into this as they start moving to form regions. By default, if you use the VSTO template for creating a form region in Outlook, the item is leaked. This can show up in a number of different symptoms, but…


Stehle’s finally doing his OOM series

I’ve been encouraging him to blog his “Matt Stehle’s Tenents of OOM Programming” for a while now, and he’s finally begun with a series on some common pitfalls we see with developers using OOM in .NET. This first article is concerned with a common reason we see for events to stop firing in your VSTO add-ins….


HOWTO: Exposing your VSTO 2005 SE Add-In to External Code

So with regular COM AddIns in Outlook, to expose your COM Add-In to external applications involved setting the Application.ComAddins.Item(“ProgID”).Object property equal to an instance of the object. Typically, in your OnConnection event handler, you’d do something like this: Application.ComAddins.Item(“PROGID”).Object = Me That allowed external code to get a reference to your COM addin class through…


VSTO add-ins and the NewInspector Event

VSTO add-ins for Outlook are great. It’s much easier than implementing the IDTExtensibility2 interface. Basically, the way it works is this (actually, Andrew Whitechapel does a much better job explaining than I will, so here you go): the AddinLoader.dll keeps a “dormant” list of add-ins that tried to load when the Outlook.exe process is started….