{"Could not load file or assembly 'AssemblyName, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)":"AssemblyName, PublicKeyToken=null"}
I'm getting the message in question as an InnerException.Message
while trying to debug my application after signing the unsigned third-party assemblies it is using.
The weird thing is that I have already signed the assembly shown in the message, the one that can't be loaded.
What could the problem be here? How can I resolve this?
EDIT
Editing to give more information on what I did:
The assembly that throws the exception, btw the project builds fine it's a runtime exception I'm getting on InitializeComponent()
of that assembly, is an open source component with WPF controls (MahApps.Metro). I've found a similar question but none of the answers there fixed the issue.
How to force WPF to use resource URIs that use assembly strong name? Argh!
PublicKeyToken = null tells you that the CLR is looking for the unsigned assembly. Since you signed them, that's not going to work well and this kaboom is expected.
You will have to rebuild the program so it uses the updated signed assembly and embeds the non-null PublicKeyToken into the manifest. You may have to remove the existing assembly reference and add it back, it isn't clear from the question whether you built the program using an unsigned copy.
Use the Fuslogvw.exe utility if you still have trouble.