Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Sign Assembly with a Strong Name

See original GitHub issue

Recently BenchmarkDotNet took dependency on Capstone.NET. We are very happy, as it has allowed us to very quickly implement a solid arm64 disassembler. But there is one problem… BenchmarkDotNet is a strong-name assembly (https://github.com/dotnet/BenchmarkDotNet/commit/5876f573b1d566d4a9048ef2b78cb8e196eea6b6 https://github.com/dotnet/BenchmarkDotNet/issues/101) and because of that, when we try to use the disassembler on .NET Framework we get an exception:

Could not load file or assembly 'Gee.External.Capstone, Version=2.2.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)

It’s not a problem with .NET Core, because this concept has been removed in Core.

@9ee1 is there any chance you could add strong name signing to Capstone.NET? I know it’s a relic of the past, but we (BenchmarkDotNet) still support .NET Framework and it would be great to have the arm disassembler on it too.

Issue Analytics

State:
Created 10 months ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

9ee1commented, Dec 1, 2022

I just published V2.3.0 @adamsitnik. Thanks again for your help on this.

1reaction

9ee1commented, Nov 30, 2022

Thank you for the information @adamsitnik. I’ll get to working on this and hopefully publish a new release within the next couple of days.

Top Results From Across the Web

Strong-named assemblies

A strong named assembly is generated by using the private key that corresponds to the public key distributed with the assembly, ...

Sign strong name assemblies with SignTool

A strong name consists of the assembly's simple text name, version number, and culture information (if provided), a public key and, a digital...

Why use strong named assemblies?

Strong name protect the version lineage of an assembly. A strong name can ensure that no one is able to produce a subsequent...

Create and use strong-named assemblies

A strong name consists of the assembly's identity—its simple text name, version number, and culture information (if provided)—plus a public key and a...

Strong named assemblies — To sign or not to sign?

Strong named assembly can only reference other strong named assemblies ... According to Microsoft, you should strong sign your dlls [link].