Re: Strong-name and remoting
From: Shel Blauman [MSFT] (sheldonb_at_online.microsoft.com)
Date: Mon, 19 May 2003 16:47:49 -0700
This does appear to be a remoting question.
-- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "Ice" <firstname.lastname@example.org> wrote in message news:e36Oz%23kGDHA.email@example.com... > I'm pretty sure that non strong-named assemblies can call strong named > assemblies, i think the issue is that strong-named assemblies can only call > other strong-named assemblies. > > ice > "Shel Blauman [MSFT]" <firstname.lastname@example.org> wrote in message > news:eMdaEpjGDHA.1776@TK2MSFTNGP10.phx.gbl... > > Is the assembly calling your test assembly strongnamed? It sounds like > you > > are running into a non-strongnamed assembly calling a strongnamed > assembly. > > Only a strongnamed assembly can call another strongnamed assembly unless > the > > AllowPartiallyTrustedCallersAttribute is applied. > > > > Shel > > > > -- > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > Use of included script samples are subject to the terms specified at > > http://www.microsoft.com/info/cpyright.htm > > > > > > "Ice" <email@example.com> wrote in message > > news:OX78oihGDHA.2236@TK2MSFTNGP10.phx.gbl... > > > I provided the attribute [Assembly: AllowPartiallyTrustedCallers] to my > > > strong-named assembly that is marshaled and now it works. > > > > > > Could someone please explain to me why the callers are not fully > trusted? > > > Is this due to Remoting? Is there any way to get around this or is this > > by > > > design? There is no documentation explaining and I am confused because > I > > > will require my MBV assemblies signed. > > > > > > Thanks. > > > ice > > > "Ice" <firstname.lastname@example.org> wrote in message > > > news:uzVEi%23ZGDHA.2152@TK2MSFTNGP12.phx.gbl... > > > > I've posted this on the Remoting newsgroup but I wanted to see if I'll > > get > > > > answer from someone here. > > > > > > > > Simply put I have a custom object that is marshaled by value > > > (serializable). > > > > The assembly is strong-named (signed). When the object is passed > around > > > > using remoting, I get the following error: > > > > System.Runtime.Serialization.SerializationException: Because of > security > > > > restrictions, the type TestObject.Test cannot be accessed. ---> > > > > System.Security.SecurityException: Request failed. > > > > > > > > When I don't strong-name TestObject, everything works fine. Obviously > > > > something is wrong here. The client is not a smart client, its a > simple > > > > windows exe (.NET). > > > > > > > > I have already tried adjusting the "typeFilterLevel" and this doesn't > do > > > > anything. > > > > > > > > Any ideas or suggestions. > > > > TIA > > > > ice > > > > > > > > > > > > > > > > > > > >