For information on netstat post in a networking group or google for the
information.

The RPC channel issue is real but you have to use common sense as to when
you call ReleaseComObject(). You do that mainly in loops on subsidiary
properties such as a mail item within a loop accessing the Items collection
of a folder. You never call that if you need to re-use the object again,
unless you explicitly instantiate another instance of the object afterwards.

You should always strive to declare objects at the lowest scope where they
will be needed, and release them when done with the objects, but don't
release objects you will have further use for.

Shimming provides a unique AppDomain for a managed code application. You
have to explicitly shim an addin or use VSTO, which does the shimming for
you. Either you write your own shimming code or you use the COM Shim Wizard
to create the shim for you. Shimming doesn't happen without an explicit shim
that loads your addin. If there is no shim then your code is running in a
common AppDomain and not an exclusive one.

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


"j" wrote in message
...
snip

The AddIn provides an exclusive AppDomain. Also can please explain a
litle bit about shimming??

In my code i use Marshal.ReleaseCOMObject(...). I do it because of rpc
conneciton known issue limitation.
There is a command netstat -a
What should i see there?? How can i recognize open rpc conenction in
Outlook??

Many many thanks.