I have created a common library at work, but unlike in this question, it is not published to the GAC. Instead, it is privately published to a company-specific installation folder. EDIT: all the internal apps go into this same folder. Is it still possible to apply a publisher policy, allowing older applications to use newer versions of...
I am responsible for developing and maintaining a set of common, framework assemblies that are used to build our product applications. These assemblies are relatively new and in a state of flux as new features are implemented, etc. As a result, it is not unusual for them to be rebuilt and redistributed somewhat frequently. I would exp...
I have a situation where a vendor-supplied assembly reference is messed up. Basically, it is pointing to a version of the assembly that I do not want to use. I used FusionLog to view the assembly binding log and I see these entries: LOG: Publisher policy file is found at C:\WINDOWS\assembly\GAC_MSIL\policy.11.0.iAnywhere.Data.SQLAnywh...
There is plenty of documentation on MSDN and elsewhere explaining how to create a publisher policy assembly. All of these examples use the command line tools (al.exe) to generate the policy assembly and GACUtil.exe to install the policy assembly into the GAC. OK, as far as it goes. For various reasons, I'd like to be able to replicate t...
I want to redirect consumers of dll v1 to dll v2. I will add a publisher policy in GAC for that. Must the policy be in GAC? Does this mean dll v2 itself must also reside in GAC? ...