mfeingold
10/21/2004 10:49:00 PM
Most certainly.
You need:
1) SecurityPermission(SecurityPermissionFlag.RemotingConfiguration) to
configure the remoting,
2) SocketPermission(NetworkAccess.Connect, TransportType.Tcp, server.Host,
server.Port) to connect to the tcp port
3) SecurityPermission(SecurityPermissionFlag.SerializationFormatter) to be
able to serialize.
You also need to apply the AllowPartiallyTrustedCaller attribute to the
assembly.
With all of this done it allowed me to connect one way. And yet another
problem - when creating the remote object IE sits there with blind screen for
20 sec or so
obviuosly waiting for somethnig to time-out, but than it wakes up and seems
to work fine.
To be honest with you as much as I admire .net remoting I am ready to give
up and replace it with plain old style socket code.