Does anyone know in details what happens when you export an application proxy
from a COM+ Managed Application, and installing the proxy on another box.
As far as I know:
- app directory created and managed dll is copied there
- COM registry entries: app id + remote server name and Cls ids pointing to
that app id
- what happens to the managed assembly, does the msi call regasm on it ?
- do you have to have all the types available in the public interfaces so
COM can resolve them ?
- does the MSI also call COM+ admin functions ?
I am sking these questions, because I want to know what dependencies this
MSI has.
Thanks.
Michael Nemtsev - 21 Jul 2006 18:38 GMT
Hello OliviuG,
Did u try to use some MSI editors, like ORCA, to find out the MSI dependencies?
O> Does anyone know in details what happens when you export an
O> application proxy from a COM+ Managed Application, and installing the
O> proxy on another box.
O>
O> As far as I know:
O> - app directory created and managed dll is copied there
O> - COM registry entries: app id + remote server name and Cls ids
O> pointing to
O> that app id
O> - what happens to the managed assembly, does the msi call regasm on
O> it ?
O>
O> - do you have to have all the types available in the public
O> interfaces so COM can resolve them ?
O>
O> - does the MSI also call COM+ admin functions ?
O>
O> I am sking these questions, because I want to know what dependencies
O> this MSI has.
O>
O> Thanks.
O>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour
"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche