This is just a guess but the effective security policy is the intersection of the policies for four different levels: Enterprise, Machine, User and AppDomain. This basically means that each level can only further restrict the effective policy established by the other levels. Maybe you're trying to widen the user policy applied to the assembly but it isn't effective because another level has imposed restrictions that apply to the assembly.
-- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/Products.aspx -----Original Message----- From: Chris Sells [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 3:33 PM To: [EMAIL PROTECTED] Subject: [DOTNET] SP1 and trusting an assembly? When attempting to trust an assembly on my intranet (on my machine, actually) using the Trust an Assembly wizard, if I choose to just trust "This one assembly", the next page says: "Due to your existing security policy, the wizard is unable to increase the level of trust for this assembly. No changes were made to your policy." What is it about my "existing security policy" that stops me from trusting a particular assembly? The assembly is signed and I'm able to trust all assemblies with that key, but not just that one assembly. This is safer?!? Chris Sells http://www.sellsbrothers.com/ You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
