Hi Mattias. I haven't changed the trust level of locally-running assemblies; so, yes it would be running with full trust.
That explains my troubles, thanks. Maybe I'm missing something; but don't all strong-named assemblies have full-trust? i.e. there is an implicit LinkDemand for full trust for all strong-named assemblies. That being the case, doesn't this new policy of "full-trust means full-trust" make StrongNameIdentityPermissionAttribute redundant? (ergo all identity permssion attributes) I guess my next dilemma is trying to figure out how to declaratively limit loading of an assembly, class, or calling of a method based upon identity of the loader/caller. Which is sounding like I need to write a new attribute class that doesn't derive from CodeAccessPermission. On Wed, 15 Feb 2006 18:40:48 +0100, Mattias Sjögren <[EMAIL PROTECTED]> wrote: >Peter, > >Is the code running with full trust? In v2.0 (unlike previous versions), >identity permission demands always succeed for fully trusted code. See > >http://blogs.msdn.com/shawnfa/archive/2005/05/17/418729.aspx =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
