Originally Posted by LibX
Still removing the strong name works in some cases but with bigger apps that have signed satalite DLL's its useless since the public key token is used to make sure its the right DLL not just some DLL with the same name.
So its better to patch the strong name token (next RE-Sign will have this function) then resign it.
Also i found lots of apps that don't even work without a strong name.
LibX // RETeam
As I understood, and tried for some applications (it works) you have to patch both, mainexe public token that is strong name for itself, then to patch public token related to satelite dll in mainexe, then you can patch satelite's dll public token that is strong name for itself. If you have A.dll that loads another B.dll and M.exe that loads A.dll, you have to do hard patching if you want to modify B.dll.
1. You have to remove SN from B.dll
2. You have to remove SN from A.dll, and token related to B.dll
3. You have to remove SN from M.exe and token related to A.dll
after all of that it will work. with modified B.dll. Recently I've dealt with activeX for NET that worked in this manner, A was main activeX dll, B was dll for time checking, and compiled application was M.