Caching of Policy Information???

From: John Murray (jtm_at_io.com)
Date: 04/24/04

  • Next message: Alek Davis: "Re: Decryption Performance" 
    Date: Fri, 23 Apr 2004 17:27:04 -0700

                I am not seeing changes made in policy without an application
    restart, and am wondering if it is something that I am doing, or expected
    behavior. Any assistance is appreciated.

                In a dynamically created AppDomain (so that I know the assembly is
    not already loaded, and so that I can unload the assembly when done with
    it,) I am loading an assembly, and evaluating it to ensure that it has
    appropriate permissions. I'm doing this through:

    SecurityManager.ResolvePolicyGroups(asm.Evidence);

    and then walking the IEnumerator (and child CodeGroups) returned. Even
    though the AppDomain was created after the changes (for instance setting
    FullTrust on an Assembly that was marked as Nothing at the time of
    application start) were made through the .NET Configuration 1.1 cp applet
    (Runtime Security Policy,) the changes are not reflected until after I
    restart the main application -- they continue to show Nothing. If I close
    and restart the application, the change is reflected.

    This makes me think that the Policy information might be cached at by the
    process and used for any child AppDomains created in the process...is that
    the way that it works? -- tia

  • Next message: Alek Davis: "Re: Decryption Performance"