Outlook 2007 Add-in woes

I have been developing/maintaining an Outlook plugin for over a year. It works fine with Outlook 2003, as well as Outlook XP.

Unfortunately, during my testing with the Outlook 2007 Beta 2 version, I've run into some problems. It seems like enabling my add-in causes Outlook to throw an exception when it exits.

I am using a debugger and Application Verifier to try to solve it, and this is what I've come up with:

When the add-in is enabled, I receive the following error from Application Verifier on exit:

=======================================
VERIFIER STOP 00000202 : pid 0xC38: Freeing heap block containing an active critical section.

0B65AB98 : Critical section address.
00000000 : Critical section initialization stack trace.
0B658AE0 : Heap block address.
00003520 : Heap block size.

=======================================
This verifier stop is continuable.
After debugging it use `go' to continue.
=======================================

If I then break into the code with the debugger, the stack trace shows this:

> ntdll.dll!_DbgBreakPoint@0()
vrfcore.dll!01483714()
ntdll.dll!_RtlpDebugPageHeapFree@12() + 0x1ba
ntdll.dll!_RtlDebugFreeHeap@12() + 0x2c
eeeeeeee()

Again, this ONLY happens when my add-in is disabled, and I have even tried disabling all of its functionality so that all it does is load and unload, but the problem persists - even without my add-in doing anything.

I'm wondering if this is a problem with Beta2 or my add-in. Any thoughts

Answer this question

Outlook 2007 Add-in woes

Gareth Hunter
Have not seen a reply. Please create a new post if this issue is not resolved.

Mike
AaronTM
Hello, I had a few questions so I can answer/find someone to answer your question or help you with your answer.

1. Is this a VSTO add-in

2. If so, have you installed VSTO SE

Thanks,

Mike
NBaig
Ryan,

I'm not clear from your message about when you see the error. First you say that the app verifier message only occurs when you are running with your add-in enabled, and then you said it only happens when your add-in is disabled. Could you clear that up

For Outlook 2007, we did make a change that means any exceptions or errors thrown/raised by the add-in are no longer caught, but instead cause Outlook to crash. This makes it easier for add-in developers to debug issues in the add-in, and easier for us to track down those issues. Are you by any chance using the COM Shim Wizard for your shared add-in I know there is at least one crashing issue in the generated COM shim that might cause a similar problem.
Outlook 2007 Add-in woes

Answer this question