Does code-signing without strong-naming leave your app open to abuse?

Question

Trying to get my head around authenticode code-signing and strong-naming.

Am I right in thinking that if I code-sign an exe that references a few dlls (not strong named)

Answer 1

you must also remember that Code Signing often introduces lots of pain when upgrading dll's without deploying other parts of the application.

This is why many popular libraries do not strongly name the dll's