Flimsiness of Outlook OM

[john bailo]

I notice a certain 'flimsiness' to the Outlook OM.

After running a c# interop against it, the OL client
seems to degrade to the point where I have to
stop/start OL, or log out or reboot to restore
functionality ( such as the MarkAsRead )
property.

[Jay B. Harlow [MVP - Outlook]]

Re: Flimsiness of Outlook OM

John,
Are you releasing your Outlook objects in the correct order?

Specifically are you using
System.Runtime. InteropServices .Marshal.Releas eComObject to release each COM
(Outlook) object when you are done with it. I understand that you need to be
certain to release children objects before releasing parent objects.
(release Outlook.MailIte m before you release Outlook.Applica tion).

Note you may need to call ReleaseComObjec t repeatedly to ensure that the
returned reference count of the RCW is zero.

Also in case you did not know the following site provides a number of useful
articles on using Outlook with .NET:

http://www.microeye.com/resources/res_outlookvsnet.htm

Hope this helps
Jay

"john bailo" <jbailo@vestcom .com> wrote in message
news:17ae505442 b3bd2dcca64fd69 fa354a8@news.te ranews.com...[color=blue]
> I notice a certain 'flimsiness' to the Outlook OM.
>
> After running a c# interop against it, the OL client
> seems to degrade to the point where I have to
> stop/start OL, or log out or reboot to restore
> functionality ( such as the MarkAsRead )
> property.
>
>
>[/color]