Problem in Automatic Deserialization of Low typeFilterLevel

Hi All

< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /> 

            I’m developing client/server windows application, using server activated remoting in v1.1.

 

All of my assemblies are signed with a strong name.

In one DLL I’m having a class (say X) which is marked with [Serializable], coz this is passed as parameter from client to server.

 

When I run the application and a method in server by passing an object of type X its throwing an error saying


"Because of security restrictions, the type X cannot be accessed."


 I'm getting this error only when my assemblies are signed with strong name


To solve this I’ve added typeFilterLevel="Full" in both client and server remoting configuration files, It works fine. So, basically it’s a problem of “Automatic Deserialization”, it requires  typeFilterLevel="Full". But when I see the MSDN document for “Automatic Deserialization in .NET Remoting” the criteria for typeFilterLevel = “Low” is matching for my scenario but still it’s not automatically deserializing why

 

One of the Criteria for “Low” typeFilterLevel  is :

Custom types that have strong names and live in an assembly that is not marked with the AllowPartiallyTrustedCallersAttribute attribute.

 

Which is same as my scenario, but why it’s not working

Thnaks & Regards
Karthikeyan



Answer this question

Problem in Automatic Deserialization of Low typeFilterLevel

  • MattWilkinson2006

    That may be a doc bug.

    I am looking into it.


  • Idiot19

    Hi Karthikeyan,

    Did you find solution to your problem If not is it possible for you to share your code

    -Gagan


  • Problem in Automatic Deserialization of Low typeFilterLevel