This entry will bore all of you except for maybe Tommy.
This is a .NET related error. Strongly named assemblies (aka signed assemblies) can only reference other strongly named assemblies. Strongly named assemblies can not reference simply named assemblies (aka unsigned assemblies).
I saw this problem when trying to run an application that was compiled against a signed assembly, but I was attempting to run it against an unsigned assembly. You can determine if an assembly is signed or not by loading the assembly in ildasm, Microsoft’s .NET assembly disassembler. It comes with the .NET SDK. If an assembly is signed then it’s manifest will contain a publickey setting that is about 10 lines of hex characters.
Ain’t that a bitch.
Strong-named assemblies suck. I did get excited when I read the title though, but then I already knew all that stuff so I got kind of bored.
Hahaha, I know you totally didn’t mean it that way but you sounded like such a jerk when you were like “Mark, what you had to say bored me.”
=) no bad feelings, the strong-named assemblies, they bring out the worst in me.
“Butch”… that’s a strong name.
“What does it mean?”
I like how there’re so many comments to this entry and I don’t even know if you’re speaking English.
“I’m an American, our names don’t mean shit.”
Haha, as they do in all of us. ;)
For me, this helped…
Boring or not,
I received this error and was “contemplating” (if you could use that word about an error in .NET) whether what you say, is the reason. Now I know it is.
I do, I do! I don’t think I’ve ever actually done it though.
I’m new here, just wanted to say hello and introduce myself.