Hi,

I've asked this in many other newsgroups but was in vain, hope someone can
offer me help here...

I've created a com+ ServicedComponent and has installed it in the COM+
catalog (in XP Pro) thru dcomcnfg. However, when I export it as an app proxy
and install it on another client machine (XP Pro), it failed with error
"Error registering COM+ application".

The client machine has a clean XP Pro.

After many tedious tryings by all sorts of installation of software (like
service pack and stuffs), I finally find out one way to make the app proxy to
be successfully installed, but it is ABSOLUTELY queer and strange...

It is that, I have to install BOTH the .NET FX 1.1 and .NET FX 2.0 on the
client machine!!!

Either you install only 1.1 or 2.0, it will simply fail to be installed. But
if I installed both dotnetfx and installed the proxy, it can install, and it
can invoke the remote methods on the server perfectly.

What I want to ask is: is there other way to allow the successful installing
of the app proxy, other than installing the FX of 1.1 and 2.0?

What I want to achieve is to have a VB6 client to invoke the
ServicedComponent on the server side, and that won't make sense if I have to
install the runtime on the client machine, especially if both 1.1 and 2.0 are
needed!

Any help will be appreciated, thank you.