I have been trying to get a project using SAO, interfaces and a factory
design as suggested by Ingo Rammer in his advanced .net remoting book.

The remoting error I am getting is Type Not Found when I try and load
an object.

The interfaces are loaded into their own project and compiled as
elantis_Interfaces.dll and have been copied to the server directory and
referenced in the client project.

The Server object is compiled to elantis_BUS.dll and contains the
classes for the remote object and the remote factory.

Client config file

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.runtime.remoting>
<application>
<channels>
<channel ref="tcp" port="0">
<clientProviders>
<formatter ref="binary" />
</clientProviders>
<serverProviders>
<formatter ref="binary" typeFilterLevel="Full" />
</serverProviders>
</channel>
</channels>
<client>
<wellknown type="elantis_Interfaces.ICountry_RF,
elantis_Interfaces" url="tcp://server:8001/ICountry_RF"/>
</client>
</application>
</system.runtime.remoting>
</configuration>


Server Config File

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.runtime.remoting>
<application>
<service>
<wellknown mode="SingleCall"
type="type=elantis.BUS.FACCountry, elantis_BUS"
objectUri="ICountry_RF"/>
</service>
<channels>
<channel ref="tcp" port="8001">
<serverProviders>
<formatter ref="binary" typeFilterLevel="Full" />
</serverProviders>
</channel>
</channels>
</application>
<customErrors mode="OFF"></customErrors>
</system.runtime.remoting>
</configuration>

Any help with this could put a smile back on the face of a really
disheartened programmer.

Thanks

No thoughts on this anyone?????

Roey wrote:
In the client process or on the server?
Examine the complete StackTrace of the Exception - the word "rethrown"
is a giveaway that the problem is server-side.

Referenced from /where/? Does the run-time client have a copy of this
Dll that it can /find/? Is it in the same directory as the client program?

On the server, how does the hosting server process "find" the Dll?
The assembly does not appear to be strongly named, and so can't appear
in the Global Assembly Cache, so how is the hosting servier (IIS) going
to locate it?


Personally, I would strongly name the DLL, load it into the Global
Assembly Cache on the server machine, then deploy a copy of it into the
same directory as the client program.

HTH,
Phill W.