That was the first path I started down, but it turns out not to be that easy to do. The IL for the attribute ends up looking like this (just the start)
.permissionset linkcheck = (3C 00 50 ... // <.P.e.r.m. for a SecurityAction.LinkDemand (or .permissionset demand for a SecurityAction.Demand). So I'd have had to work harder that I wanted :-) to type in the hex representation of an additional serialized permission). That's what caused me to just point to an xml file that I built that had the serialized permission set with two strong name identity permissions in them. Another idea to try just occurred to me. Will post back later... -Mike http://staff.develop.com/woodring http://www.develop.com/devresources > 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.
