Geek Answers Handbook

How to enable ConfuserEx warning for missing SN keys

I have a project with a .NET library that I messed up with ConfuserEx. During the protection run, I received a warning that states the following:

[WARN] [foo.dll] SN Key is not provided for a signed module, the output may not be working.

The fact is that the assembly is signed with a strong key name. However, after that, the code seems to work without problems.

Two questions arise:

  • How do you detect the actual problem if the output fails?
  • How do I provide an SN key to get rid of the warning?

Neither the software documentation nor the cli output gave me directions on how to include the keys. Copying the key to the same folder as the DLL did not resolve the warning.

+4
source share
1

gui ConfuserEx . . !

ConfuserEx Description how to add a key to sign the confused assemblies

.crproj 2 snKey snKeyPass, :

<module path="foo.dll" snKey="fooKey.pfx" snKeyPass="fooKeyPassword" />
+5

More articles:


All Articles