binding to Strongly named asembly in my directory rather than GAC

with strongly named assemblies the load order seems to give the GAC
trumps. So far assemblybinding redirects are only good if the versions
are different. However in my Case the strong name, and version number
are the same, even though the contents are very different and
effectively a different version. The vendor choose to do so all
existing software that bound to their library would still work with
their "V2". However in my application i distribute the DLL locally and
want to force it to bind to the "V1" that is in my directory. Even if
i explicitly specify the filename of the assembly to load the "V2"
assembly from the GAC gets loaded if it exists.

Is there any technique whether assemblybinding redirect , or otherwise
that would help me achieve what i need