Publisher Policy — Highest version, which highest?

When there are multiple publisher policy assemblies for the same assembly, the highest version of publisher policy assembly will be used.

Turns out there is a bug in .Net framework v1.0/v1.1, that the alphabetic higest version, instead of the numeric highest version of publisher policy assembly is used.

This bug will be fixed in the next service pack release for .Net framework v1.0/v1.1.

Until then, you have to work around the bug by either making sure only one publisher policy exists for the assembly, or the numeric highest version of publisher policy is also the alphabetic highest version.

What an odd bug to have found. Do you have any examples that demonstrate this so we’ll know what to watch for? It would be nice to have an example of one so we can write our test code to ensure that our production code does not have the same bug.