Remoting exception when upgrading from .Net 1.0 to .Net 1.1

  • Thread starter Thread starter Mads
  • Start date Start date
M

Mads

Hi,

we are trying to upgrade our application from .net 1.0
to .net 1.1 framework.

We get the following exception:
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

We have read a number of posts (including
http://www.ingorammer.com/remotingFAQ/changes2003.html)
and tried to set the typeFilterLevel to "Full" as
suggested.

It did not change the problem, we still get the same
exception.

We have looked at some Remoting samples. The difference
to our application is that we start the remoting with
this function call:

RemotingConfiguration.Configure(remoteConfigFile);

We have a sample project that exposes the problem - can
we upload that to you?

br
Mads
 
Now we tried to follow the ingorammer directions, but set
the typeLevelFilter programmatically instead of
using .config files. And now it works.

So it seems that settings in the server config file has
no effect?

We only set the typeLevelFilter for the server exe.

br
Mads
 
Hello Mads,

Thanks for your post. You are running into an incompatible issue between
..NET Framework 1.0 and 1.1. This issue is documened at

Secure Serialization in .NET Remoting - Backwards Breaking Changes from
version 1.0 to 1.1
http://www.gotdotnet.com/team/changeinfo/Backwards1.0to1.1/default.aspx#0000
0153

Please feel free to let me know if any further is needed.

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Back
Top