Assembly.LoadwithPartialName vs Assembly.Load

Isn't it true that when we want things done 'right' it generally means we have to do more work? This is true for loading assemblies in .NET 2.0. Remember the good old days of loading DLLs in Win32 using LoadLibrary and simply specifying a DLL name? Sure, it was easy and straightforward, but it led to countless hours of contractors dollars wasted on untangling DLL Hell.

Using a framework that promises to rid us of DLL hell means we need to me more precise when loading Assemblies. This is why 'LoadWithPartialName' has been depricted in v2 .net.

But can't there be a happy medium? What if the DLL I'm loading is part of a shared framework that my organization has control over. What if we can guarantee backward compatibility and all I want to guarantee is that the latest version is always loaded?