These links may help some:
https://msdn.microsoft.com/en-us/library/s1sx4kfb(v=vs.100).aspx
https://msdn.microsoft.com/en-us/library/xwb8f617(v=vs.110).aspx
As MSDN states as well:
Quote:
|
When you reference a strong-named assembly, you expect to get certain benefits, such as versioning and naming protection. If the strong-named assembly then references an assembly with a simple name, which does not have these benefits, you lose the benefits you would derive from using a strong-named assembly and revert to DLL conflicts. Therefore, strong-named assemblies can only reference other strong-named assemblies.
|
So from the look of things you are required to keep the strong-name on your exe in order for it to load those modules. Bypassing though, I am not sure. I tend to not ever really use strong names on anything I make so I've never personally had to deal with it.