Helmut, I've done a lot of small Outlook development over the years but I usually wrote code directly in IDTExtensibility or VSTO classes, and I've never had to write anything complex for inspectors. So I never looked close at your wrapper classes until today. I'm working on a project that requires adding buttons to the new/reply to email inspector. I understand the wrappers, but I'm wondering why someone would want to put code in a wrapper.  Can you provide a couple case examples where this would be helpful?  As an example, when a user launches a Reply window I need to provide a button to allow them to get information from a server.  Why would I wrap the inspectors when they're opened rather than adding buttons more "directly"?

I'm guessing that rather than just having a general purpose InspectorWrapper, that you expect developers to create specific InspectorWrappers, like in my case ServerInfoInspector?  Then when an Inspector is launched we can add it to one or even more specific-purpose wrappers to have each operate on it as necessary.

LOL - have I answered my own question or do you have better examples?  Thank you very much.

Hello Starbuck:

Why someone need to use Wrappers for Inspectors?

Thanswer is:

Because A User can have multiple Windows Open and Closed at any time. You need a way to identify your Windows.
It's easier to create different Wrappers for different kind of Outlook-Windows - like ContactItem, TaskItem etc.

It's also easier to avoid Memoryleaks and do Tracing in case of Errors.

It's just an approach to write more robust Outlook Extensions.

Hope this helps, Greets-Helmut