Codesys installation package fails because not signed

2022-05-09
2024-04-18
  • randomplcguy - 2022-05-09

    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?

     
  • randomplcguy - 2022-05-10

    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.

     
  • randomplcguy - 2022-05-10

    Never mind, I found why.

     
  • randomplcguy - 2022-05-10
     

    Last edit: randomplcguy 2022-05-10
  • randomplcguy - 2022-05-10

    The procedure you gave was to sign the library, not the package. For future reference you need to use PackageManagerCLI.exe to do so.

     
  • davecfc - 2024-04-18

    Also had this problem when working on legacy project. My packege was CODESYS Code Generator ARM 4.0.3.0.package. To manage this I used PackageManagerCLI.exe. This tool does not validate certificates appearently. My command: "C:\Program Files\CODESYS 3.5.17.30\CODESYS\Common\PackageManagerCLI.exe" --profile="CODESYS V3.5 SP17 Patch 3" --install=""C:\Users\sample_user\AppData\Local\Temp\APInstaller\5wx1k02a.r2t\CODESYS Code Generator ARM 4.0.3.0.package""

     

Log in to post a comment.