Yes, I suspect the original intention of the API was to compare version, public keys etc. too, but as confirmed by the Connect bug it simply never behaved like that.
They couldn't change the behavior afterwards for compatibility reasons, so this is why the MSDN docs for newer framework versions mention that it just compares the simple assembly name (i.e. the AssemblyName.Name property).
Removing the call to this API and replacing it with a simple compare of the two AssemblyName.Name properties should work IMHO, since this is all that the API does anyway.
They couldn't change the behavior afterwards for compatibility reasons, so this is why the MSDN docs for newer framework versions mention that it just compares the simple assembly name (i.e. the AssemblyName.Name property).
Removing the call to this API and replacing it with a simple compare of the two AssemblyName.Name properties should work IMHO, since this is all that the API does anyway.