Modern day DLL hell

It's been a while, so I figure I'll put some random technical information on the web. At work, I just used ildasm and ilasm to take apart a Microsoft interop dll (Microsoft.Vbe.Interop.dll to be specific), change a reference to another DLL to use a hash of a privately signed copy, and then reassembled the DLL signing it with our private key. Short term, this allows us to workaround some fun with Visual Studio when it copies DLLs to the output directory and there are multiple DLL references with the same filename, but different strong names. Less concretely, this should help work around some issues that we see from time to time where users have messed up Office PIA installations.