Hey Mike,
here is the info you asked for:
Please note: I'm developing with .NET Framework 1.1 therefore I had to add
the <serverProviders> tag to deal with the security changes from 1.0.
Client Configuration File
--------------------------
<configuration>
<system.runtime.remoting>
<application name="ClientApp">
<client url = "tcp://<Omitted for security>:8085/ServerObject">
<activated type = "IRDALib.ServerObject, IRDALib" />
</client>
<channels>
<channel ref ="tcp" port="8090">
<clientProviders>
<formatter ref="soap" />
</clientProviders>
<serverProviders>
<formatter ref="soap" typeFilterLevel="Full"/>
</serverProviders>
</channel>
</channels>
</application>
</system.runtime.remoting>
</configuration>
Server Configuration File
---------------------------
<configuration>
<system.runtime.remoting>
<application name="ServerObject">
<service>
<activated type="IRDALib.ServerObject, IRDALib" />
</service>
<channels>
<channel ref="tcp" port="8085" >
<serverProviders>
<formatter ref="soap" typeFilterLevel="Full" />
</serverProviders>
<clientProviders>
<formatter ref="soap" />
</clientProviders>
</channel>
</channels>
</application>
</system.runtime.remoting>
</configuration>
----------------------------
- I'm using a console application as the hosting environment for the server
during development.
- Both machines are running on a company network behind a firewall. I'm
checking with the system admin if any network address translation occurs
within the local network but, without knowing how the network is
configured, I would have thought this kind of thing happens at the
intranet/internet boundary. It changes my perception of the usefullness
of .NET Remoting if you can't even deploy it on an intranet without the
risk of a system admin change rendering the application useless.
