Vista - Remoting and ActiveX - Location of .Net Assemblies

I have a VB6 ActiveX exe application that uses a .Net DLL that is exposed as
a COM DLL. The VB6 application is stored in ParentFolder. The .Net DLL is
stored and registered in ChildFolder. I have several other .Net DLL's (Com
exposed) loaded in ParentFolder that are used by the VB6 app. I have 2 setup
programs to install the software. The main server software is in
ParentFolder, the optional special software is loaded to ChildFolder only
when needed.

The .Net DLL does a remoting call to another computer that is setup as the
remoting server, hence the server is now the client. The response from the
remote computer is returned but the application fails because of a missing
assembly. The missing assembly is present in ChildFolder not ParentFolder.

This works just fine if the 2 software systems are installed in the same
folder.

It appears that on the return from remoting, the location of the original
VB6 application is used to look for the .Net assemblies instead of the COM
registered location, ChildFolder.

Is there a way to specify the location of the assembly so that I can keep
the 2 folder architecture???

The remoting config file contains very little info:

Client Remoting config file:
<configuration>
<system.runtime.remoting>
<application>
<channels>
<channel ref="tcp" secure="true"
TokenImpersonationLevel="identification" port="0" />
</channels>
<clientProviders>
<formatter ref="binary" />
<formatter ref="soap" />
</clientProviders>
<serverProviders>
<provider ref="wsdl" />
<formatter ref="soap" typeFilterLevel="Full" />
<formatter ref="binary" typeFilterLevel="Full" />
</serverProviders>
</application>
<customErrors mode="Off"/>
</system.runtime.remoting>
</configuration>
--
Steve G