views:

15

answers:

0

My understanding is that as soon as .NET fires up the RCW to access a COM object, the security credentials are persisted within the COM context until the .NET application is closed... thereby preventing the use of different credentials later on during execution.

There is a RCW wrapper on Codeplex that I think will allow me to take a given COM object, and use a different security context with it.

http://dcomshim.codeplex.com/

Is this still the current best way to create multiple sessions from .NET when using a COM object, each with it's own security context?