COM+ and dependent COM+ assemblies to client

i have a client application cli calling COM+ assembly (comA) thru application proxy (exported from the server machine). comA references other COM+ assemblies such as comB, comC and comD. Now the client cliA does not talk to comA until you copy the assemblies comB, comC and comD into the folder of the cliA.

It is kinda weird, even though you write a 3-tier architecture, during deployment, we have to distribute all the COM+ assemblies onto the client for it to work in .NET! this was not the case in VB6 world.

Anyone know how to avoid distributing the dependent COM+ assemblies?

Thanks.

[607 byte] By [nd_ramesh] at [2008-2-15]