I have a dll that I am deploying to the GAC.  I have had 3 releases of the
dll: 1.1.5.0, 1.1.20.0 and my current release 1.2.10.0. Now, I have used a
publisher policy deployed to the GAC in the past with the following name:
policy.1.1.myAssem.dll. As soon as I go to v 1.2.10.0, my publisher policy
does not work. I have to create a new publisher policy for the 1.2 release
called policy.1.2.myAssem.dll. This sounds really crazy and unmaintainable
to me.

Is there a way I can always deploy one and only one publisher policy that
will take all versions to a particular version of the dll (the latest one)?
I think Microsoft did this to avoid the DLL hell in the COM days, but it is
making everybody's life a little difficult because all we want to do is
redirect to the latest version of the dll (without touching the application
code or config files).

Thanks,
MT