NGWS SDK Documentation  

This is preliminary documentation and subject to change.
To comment on this topic, please send us email at ngwssdk@microsoft.com. Thanks!

Step 5: Administrator Policy

The final step in the binding process is to apply any version policy specified by the administrator. Admin policy is specified in a file called admin.cfg located in the windows directory. The syntax for specifying admin version policy is that same as that used in the application configuration file. The following example redirects all references to “calcr” made by any application on the machine to version 5.0.11.0:

   <BindingPolicy>
      <BindingRedir Name="Calcr"
                    Originator="32ab4ba45e0a69a1"
                    Version="*" VersionNew="5.0.11.0"
                    UseLatestBuildRevision="yes"/>
   </BindingPolicy>

Administrator policy is the strongest form of policy. The version determined by the administrator policy file is final, and cannot be overridden. It is required that if a policy redirect occurs as a result of administrator policy, the target version MUST pre-exist in the global assembly cache. That is to say that the AssemblyResolver will not re-issue a probe for the post-administrator-policy assembly, but rather it is assumed that such version redirect is a result of an explicit administrator action, which involved pre-installing the desired target assembly in the global assembly cache.