No, it is not necessary to be static, not even a add-in member
field/property. The only requirement is that an instance of a class that is
returned from a RequestComAddInAutomationService event handler is
implementing a given COM interface.
I am using code like this:
protected override object RequestComAddInAutomationService()
{
PreInitialize();
return new PreInitializeData(factory, client);
//return base.RequestComAddInAutomationService();
}

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

I believe that static is a requirement, but I'm not positive. Try it without
and see if it works. If it doesn't that still lets you set the externally
visible interfaces as static and still work with non-static methods and
properties.

--
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


"Nenad" wrote in message
...
Thanks, that is exactly what I have asked for.

One final question: As I can see, using this technique, only static
methods
and properties can be invoked on add-in class?