You'll probably need to not define the refusal on the assembly but deny access to your methods programmatically. I believe the assembly level refusal will be enforced by the runtime and you'll never get a chance to "opt out" in your code. I don't think there is a runtime API to fiddle with your assemby's security settings. So in this instance, you'll have to not do "declarative programming" and program the old-fashioned way.
Kenneth Brubaker
----Original Message Follows----
Lets say I have:
Assembly A thas has custom permission P1. Assembly A defines class AC;
Assembly B that is refused custom permission P1. Assembly B defines class BC;
At runtime instance of AC deems that a certain instance of BC should be treated as safe and wants to grant it permission P1, so instance BC can directly access certain elements that it previously could not.
Is that possible?
_________________________________________________________________ Chat privately with Bon Jovi, Seal, Bow Wow, or Mary J Blige using MSN Messenger! http://www5.msnmessenger-download.com/imastar/default.aspx
=================================== This list is hosted by DevelopMentor� http://www.develop.com NEW! ASP.NET courses you may be interested in:
2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet
Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet
View archives and manage your subscription(s) at http://discuss.develop.com
