As soon as the OVC is instantiated (runtime AND design time), the Outlook.exe
process will run, although there will be no visual Outlook window (but any
Reminders may pop up!). There's no way around this - it's effectively a
window into an instance of Outlook, not a completely separate application.

--
Eric Legault (Outlook MVP, MCDBA, MCTS: Messaging & Collaboration)
Try Picture Attachments Wizard for Outlook:
http://www.collaborativeinnovations.ca
Blog: http://blogs.officezealot.com/legault/


" wrote:

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
OVC or the client... not both.

Additionally, if the Outlook client is not running, OVC does not
instantiate the add-in. Is this expected behavior?

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

Thoughts welcome.

Thanks in advance
-Steve