Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How does remotesoft obfuscator deal with strong named assemblies?

April 26, 2017Assemblies deal named obfuscator remotesoft strong

0

Posted

How does remotesoft obfuscator deal with strong named assemblies?

1 Answer

0

Posted

Our obfuscator deals with strong named assemblies automatically, no extra work is required. Usually, attaching a strong name signature to your code involves two steps: (1) create the strong name key using the SN utility: sn -k sample.snk (2) compile your assembly with the key by adding a declaration to the assembly to indicate the location of the key file, as shown below, C#: [assembly: AssemblyKeyFile(“sample.snk”)] class StrongNameTest { … } VB.NET: Public Class StrongNameTest … End Class Just make sure that your key file is in the correct path when the obfuscator is invoked, and our obfuscator will automatically re-sign the modified assembly with the same key file. If you do not have access to the key file, you can choose to delay sign the protected assembly, or choose to remove the signature, so you can continue to work with the obfuscated code.