+ Reply to Thread
Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Again Code signing

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default Again Code signing

    Sorry, dont wanted to post in the old Thread.

    1.) There is a bug in setup builder - if you compile with code signing (General Informations) he doenstn compile with the Code. "You" have to insert the pwd when sb6 compiles your project. Normally it inserts it automatically, but the PKEY.EXE seems to be buggy. I tried it with an older PKEY.EXE aaand - it worked.
    It would be very nice if you fix it.

    2.) Where is the code-signing in the Script Editor? I inserted the entrys in the General Information Tab and now i want it to be displayed at the script editor. Is there any way to see it there?

    Much thanks!
    Phil.

  2. #2
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Again Code signing

    Phil,

    No bug in PKEY.EXE

    Please see:
    http://www.lindersoft.com/forums/showthread.php?t=2170

    and:
    http://www.lindersoft.com/forums/showthread.php?t=2202

    I don't understand question 2, sorry. Code-signing in the script editor for your applications can be done with the "#code-sign application..." compiler directive.

    Friedrich

  3. #3

    Default Re: Again Code signing

    Thanks.

    I want to build a if-statement around the #code-sginin. (for test compilations)
    In my script you can see:
    If %CODE% equals "1" then
    #code-signin application C:\....\Project_[MAKE].exe
    End

    it doesnt care wich value the %CODE% variable contains, my setup is always code-signend.

  4. #4
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Again Code signing

    Phil,

    I fear it's still not clear, sorry :-(

    1. The General Information -> Digital Signature code-signs your installer and uninstaller. No file name required.

    2. The "#code-sign application" compiler directive can be used to code-sign your own application files (DLL, EXE, etc.). File name required.

    So what would you like to do: 1. or 2. or both

    And what should the #if statement do?

    Thanks,
    Friedrich

  5. #5

    Default Re: Again Code signing

    ah ok, i didnt know.

    First: i want both.

    2nd: i want sb6 to compile my project without signin my files and withough signin the setup itself IF the %CODE% variable isnt 1.

    i need it for test compilations.

  6. #6
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Again Code signing

    Phil,

    But %CODE% is an installer "runtime" variable ;-) It does NOT have any value when you COMPILE the script! It has a value when you RUN the installer.

    You can use compiler variables here, e.g. [CODE]

    Then use "#ifcompvar" and you are done.

    Does this help?

    Friedrich

  7. #7

    Default Re: Again Code signing

    i know. i defined it with a compilervar ... ^^

    set %code% to [code] ...
    ^^
    but ill try with this one, thanks!

  8. #8

    Default Re: Again Code signing

    works perfect!
    thanks!
    but i still need a way to compile my project without signin itself. now it doesnt sign the files (#code sign app), but thats not enough :-P

    (i love you for your ensurance!)

  9. #9
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Again Code signing

    Phil,

    You can't enable/disable the installer/uninstaller code-signing based on a compiler variable.

    But you really should ALWAYS code-sign your installer/uninstaller!!!!

    Friedrich

  10. #10

    Default Re: Again Code signing

    Hm ok.
    I know i should.
    Much Much thanks for your help!
    You are awesome!

    Best wishes!
    Your fan Phil

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts
  •