The procedure you gave was to sign the library, not the package. For future reference you need to use PackageManagerCLI.exe to do so.
Never mind, I found why.
Never mind, I found why.
Just tried the procedure, and it does not work. I can see it in the certificate store, but for some reason Codesys does not select it in the dialog.
I am trying to create an installation package for the Codesys Worbench. While it works fine for Workbench 3.5 SP16 and SP17, it fails for SP17 patch 3 and later. 3S replaced the Package Manager with Codesys Installer. While it supports packages, it fails because my package does not have a signature, even if I clicked on "I want to continue despite of the missing signature(s)". Does anyone know how to sign a package?