> System.Security.SecurityException: Type > System.DelegateSerializationHolder > and the types derived from it (such as > System.DelegateSerializationHolder) > are not permitted to be deserialized at this security level.
The 1.1 CLR errs on the side of security unless you say otherwise. To allow what you're trying to do, locate the <formatter> element in the server-side configuration file, and add a typeFilterLevel attribute like so: <formatter ref='binary' typeFilterLevel='Full'/> You're also like to run into a couple of other issues when trying to remote events: * Firewalls/NAT devices will interfere with server-to-client callbacks if the client is behind such a device. * Assembly resolution failures on the server due to the fact that 'too' much information about the client-side object receiving the event is serialized over for the server to use when building its proxy back to the client. You can find discussions on this in the archives for this list and/or the DOTNET-CLR list and/or the retired DOTNET list (don't remember which). And I have a sample of how to work around it without having to resort to putting a copy of the client EXE over on the server here[1]. -Mike Bear Canyon Consulting LLC http://www.bearcanyon.com http://www.pluralsight.com/blogs/mike [1] http://www.bearcanyon.com/dotnet/#RemoteEvents =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
