Thanks that makes perfect sense to me but I think I don't need to write
wrapper class for explorer as my requirements are very simple and nothing is
shared between the toolbar clicks that might cause the issue.

What all I want is to put toolbar whenever new explorer open and perform the
operation when button click.

Thanks a lot for your help.
Paresh

"Ken Slovak - [MVP - Outlook]" wrote:

Here's one example.

You have a toggle button that indicates a state for doing something. If you
have 2 Inspectors open and both use the same Tag value for a
CommandBarButton, both will get the click event that toggles the button. So
toggling in one toggles both. Then when some action is taken based on the
button state you can't maintain separate states for the button in each
Inspector.

Using wrapper classes solves a number of problems such as that with unique
Tag values, individually handling events in multiple open windows, handling
discrete ribbon clicks that are directed to only one Inspector where you
pass the click to a handler in your wrapper class, etc.

Every advanced Outlook developer I know uses wrapper classes and
collections, but your mileage may vary. I'd never do an Outlook addin myself
without wrapper classes.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"paresh" wrote in message
...
Ken, actually I am just wondering why we have to write the very complex
code
to handle the toolbar for all opened Outlook windows individually? I
understood your concept of generating TAG id uniquely after creating the
explorer object but I haven't noticed multiple events firing when I have
two
Outlook window open and both have same toolbar "My Toolbar" with same
Buttons
and same TAGs.

In short, could you give me a simple example where we have to use the
concept given by you and my code will not work? I am intermediate level in
add-in so I might not be aware of many things.

Thanks,
Paresh

.