.NET Remoting, passing objects into methods

Question

I am writing a .NET Remoting application. I have my dll, server, and client all working correctly. However, when I try to change my method call to take an object parameter instead of a simple type like an int, it complains with this error.

Type System.Runtime.Remoting.ObjRef and the types from it (such as System.Runtime.Remoting.ObjRef) are not permitted to be deserialized at this security level.

The method is something like this.

public List<Orders> GetOrders(int UserID) { //Works public List<Orders> GetOrders(Users user) { // Doesnt Work [Serializable] public class Users : MarshalByRefObject {

Now I have made the User class also, [Serializable] and given it MarshalByRefObject inheritance. Could this be my problem? I have tried removing [Serializable] from the User class and it complains cause it cant interpret it.

EDIT Ok, here is my client method.

IChannel channel = new TcpClientChannel(); ChannelServices.RegisterChannel(channel, false); CustomType Server = (CustomType)Activator.GetObject(typeof(CustomType), "tcp://localhost:9934/CustomType");

Here is my server.

BinaryServerFormatterSinkProvider provider = new BinaryServerFormatterSinkProvider(); provider.TypeFilterLevel = TypeFilterLevel.Full; IDictionary props = new Hashtable(); props["port"] = 9934; TcpChannel channel = new TcpChannel(props, null, provider); ChannelServices.RegisterChannel(channel); RemotingConfiguration.RegisterWellKnownServiceType(typeof(CustomType), "CustomType", WellKnownObjectMode.Singleton); Console.WriteLine("Server is initialized"); Console.ReadLine();

Have you tried by removing MarshalByRefObject from Users class? — L.B
– L.B, Commented Feb 13, 2012 at 21:14
When I removed the MarshalByRefObject it didnt help, thanks! — Steven Combs
– Steven Combs, Commented Feb 13, 2012 at 21:48
Since you were the first to post the solution L.B I would give you credit if you create an Answer instead of a comment. — Steven Combs
– Steven Combs, Commented Feb 13, 2012 at 22:27

Chriseyre2000 · Accepted Answer · 2012-02-13 21:22:14Z

4

"are not permitted to be deserialized at this security level." is the significant part.

See the following for the answer

http://www.codeproject.com/Articles/4363/NET-Remoting-in-Simple-English-Really-it-s-that-s

Set the following on both client and server:

typeFilterLevel="Full" in the Formatter tag

answered Feb 13, 2012 at 21:22

Chriseyre2000

2,0531 gold badge15 silver badges28 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Steven Combs Over a year ago

If I am not setting this up via a config file how do I perform this?

Chriseyre2000 Over a year ago

The answer is here: alexthissen.nl/blogs/main/archive/2007/12/23/…

afnpires Over a year ago

The provided link is broken. The new one is alexthissen.wordpress.com/2007/12/23/…

Alan · Accepted Answer · 2012-02-13 21:21:31Z

2

Ensure both the server and client configuration set the typeFilterLevel property to Full

or have your User class implement ISerializable

MSDN Documentation on .NET Remoting Serialization Security.

answered Feb 13, 2012 at 21:21

Alan

47k20 gold badges118 silver badges138 bronze badges

6 Comments

Steven Combs Over a year ago

Ok whenever I implement this, it gives me the following error when the method tries to hit the DB.

This remoting proxy has no channel sink which means either the server has no registered server channels that are listening, or this application has no suitable client channel to talk to the server.

Steven Combs Over a year ago

Let me be more specific, whenever it tries to access the User.UserID property it throws this exception.

Steven Combs Over a year ago

Ok so I am confused. Does this mean I need to create the same channel on the client machine as the server?

Alan Over a year ago

Yes, both your server, and client need to create the channel.

Steven Combs Over a year ago

Alan, how do I set the client so that the typeFilterLevel is Full. My Client was created like so.

IChannel channel = new TcpClientChannel(); ChannelServices.RegisterChannel(channel, false); (CustomType)Activator.GetObject(typeof(CustomType), "tcp://localhost:9934/CustomType");

|

Frederik Gheysels · Accepted Answer · 2012-02-13 21:17:20Z

1

Actually, .NET remoting is an obsolete technology. You should take a look at WCF instead.

Regarding your actual problem: Your probably running your application in a trust-level that is too low.
The Users class should be serializable, but, if it does not contain any methods that should run at the server, it should not derive from MarshalByRefObject

answered Feb 13, 2012 at 21:17

Frederik Gheysels

57.2k12 gold badges103 silver badges156 bronze badges

4 Comments

Marc Gravell Over a year ago

arguably, remoting still serves a usage for talking between AppDomains in the same process. Just sayin'

Steven Combs Over a year ago

I havent looked at WCF yet, and the User class doesnt hold any necessary calls that would need to inherit MarshalByRefObject. I was trying to go the simple route and create a single DLL that could be utilized for the Server and Client Application instead of creating multiple DLL's.

John Saunders Over a year ago

The practical problem with using an obsolete technology is that there are fewer people who remember it. I just barely remembered that I had seen this error before, but not how to fix it. And I'm old.

Steven Combs Over a year ago

Lol ok well, I am young and wanting to embrace the latest and greatest so I should probably look into WCF and figure it out. Also, I dont want to run into major issues with my new app. So thanks for the heads up on this!

Collectives™ on Stack Overflow

.NET Remoting, passing objects into methods

3 Answers 3

3 Comments

6 Comments

4 Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

3 Comments

6 Comments

4 Comments

Linked

Related