Re: Strong Name vs Serializable vs Remoting

From: Ken Kolda (ken.kolda_at_elliemae-nospamplease.com)
Date: 01/14/05 

Date: Fri, 14 Jan 2005 08:16:47 -0800

Here's an article from MSDN that might help clarify how this all works:

http://msdn.microsoft.com/library/en-us/dndotnet/html/versremote.asp

That said, I'm not sure why the strong name should give you a security
problem unless your app is running in a context that has lowered permissions
and the object you're attempting to serialize has some sort of code access
permission set on it. Can you post the exact content of the exception your
getting (message + stack trace)?

Ken

"Chris Yager" <chris.yager@gldsolutions.com> wrote in message
news:Ouoo0Fd%23EHA.2452@TK2MSFTNGP14.phx.gbl...
> What is the relationship between a serializable object, strongly named
> assemblies, and remoting?
>
> This is a post that goes hand in hand with a previous post with the
subject
> "Can't Serialize [Serializable] object to server".
>
> I have stumbled onto something... When adding remoting to the
architecture
> of my solution (this was a requirement - not an afterthough!) I had
already
> strongly named a few assemblies. One of these required serialization to
the
> server as a parameter on a remote object method call.
>
> With a strong name applied to my serializable library, serialization fails
> with the "can't serialize due to security problems" exception. When I
> recompile the assembly without a strong name, the exception goes away and
> everything works OK.
>
> My problem here is that I need to strongly name an assembly in the
reference
> chain on the server and I cannot reference a non-strong named assembly.
>
> I can continue on my quest for the solution I'm developing but any insight
> here would be greatly appreciated!
>
> -chris
>
>

Relevant Pages

  • Re: "Insufficient state to deserialize the object" error
    ... The delegate itself is a serializable object, so both client and server need ... > that requires serialization? ... >> If any of the assemblies are being loaded from the mapped drive, ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Problem with serializing business object instead of core objects
    ... code implementation deployed to the client. ... forth) in a separate DLL that is used by both the server and client. ... > serialization info), these type definitions will not be recognized as the ... > client and server assemblies. ...
    (microsoft.public.dotnet.framework.remoting)
  • is serialization really a performance hog?
    ... I'd like to hear the experience of others with object serialization at ... The server sends small objects to the clients. ... The client sends almost ... transmission of reference objects along with the small objects ...
    (comp.lang.java.programmer)
  • Re: Tactics for Debugging Custom Components with CodeDom Serialized State
    ... >I am not sure if you used the CodeDOM serialization correct, and if CodeDOM serialization is the correct solution for serializing your objects. ... They appear in the Task List window below the design surface as "Build Errors". ... considers the two assemblies to be different, ... >When the exception throws out, in the debugger call stack window, we can get the list of exception call stack. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Weird XML serialization problem
    ... I am experiencing a *very* frustrating problem with XML serialization. ... Everything works - all of my assemblies that reference ... Exception Information ...
    (microsoft.public.dotnet.framework)