What are the common issues in redirecting assemblies using the publisher policy files?
1) Make sure to follow proper naming conventions for the policy dll. For example, if the original assembly name is TestAssembly.dll then the corresponding policy assembly should be called “policy.1.0.TestAssembly.dll” to make this redirection work for all “1.0.*” version bindings of the original assembly. 2) While specifying the name for the assembly in the policy file, do not include the “.dll” extension.
Related Questions
- The MD5 Sums for My Policy/Config/Tripwire Executable Files at Installation are different than what my Latest Report tells me. How could this happen?
- How does the "Remove retention files for overlap policy" work under the Advanced Retention Policy task?
- What are the common issues in redirecting assemblies using the publisher policy files?