“A strongly-named assembly is required.”

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.

This entry was posted in All, Computers and tagged . Bookmark the permalink.

11 Responses to “A strongly-named assembly is required.”

  1. 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.

  2. Anonymous says:

    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.


  3. Anonymous says:

    I do, I do! I don’t think I’ve ever actually done it though.

  4. Anonymous says:


    I’m new here, just wanted to say hello and introduce myself.

Leave a Reply

Your email address will not be published. Required fields are marked *