On Fri, 12 Apr 2002 16:11:10 -0600, Mike Woodring <[EMAIL PROTECTED]> wrote:
>Well, I tried to work around it by annotating the method with the >PermissionSetAttribute and pointing it to an xml file containing a >serialized permission set containing two StrongNameIdentityPermissions; but >the result was the same - an empty permission set in the assembly. > >FWIW - I get the same behavior using vb.net. At any rate, seems like a bug >to me. Either we're not supposed to be trying to apply more than one >StrongNameIdentityPermissionAttribute to a single method (in which case, the >docs and the compiler should be complaining); or it's supposed to be >supported and the compilers are silently botching the job. Thanks for pointing this out, Mike. Now I'll always run ILDasm to verify that what gets put into the assembly "matches" my code :). This does seem disconcerting to a degree - I know that I'd like to at least have the ability to apply a LinkDemand to a method with more than one strong name. BTW did you try dumping your assembly from ILDasm, "fixing" the .permissionset value to contain two StrongNameIdentity values, and then ilasm it? If it's still there, does the calling code behave as expected? Regards, Jason You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
