Hello -

We have run into an issue here where an add-in that was written using
VSTO2005 for Outlook is running into a conflict with OVC if OVC and the
Outlook Client are both running at the same time. It appears to be
because they share the same process.

I won't bore you with too many details but, we are running Office 2003
pro sp2 and have all the prerequisites for the add-in to function
properly (which it does) as long as you are accessing it from either
OWC or the client... not both.

Is there a way to force OVC to use it's own explorer process?

Thoughts welcome.

Thanks in advance
-Steve