Recent content by jefc

  1. jefc

    Broken License Agreement layout in Paquet Builder 2025

    Thank you for the update. We only build our project with the directive file using the console compiler.
  2. jefc

    Broken License Agreement layout in Paquet Builder 2025

    Hello, Thank you for your quick answer. We have also tried with HTML and raw TXT file but the result is the same, it looks like some kind of "pass-through" is missing to integrate the HTML or TXT file as is. Here is the result when using an HTML file (original file layout on right side...
  3. jefc

    Broken License Agreement layout in Paquet Builder 2025

    Hello, We are including an RTF file as End-User License Agreement in our directive file as follows: [Templates] LicAg=#{pathToEula} (where #{pathToEula} is replaced by the absolute file path using a script) After upgrading to Paquet Builder 2025, the EULA layout is broken as if the RTF file...
  4. jefc

    "Can't find include file" error after upgrading to 2021.0

    Yes, we’d list them for instance either through the [Variables] or [General] section of the directive file or, even better, in a dedicated section which would be linked to the “Additional C Scripts” box in the GUI: [Cscripts] 0=C:\myscriptsdir1\script0.c 1=D:\myscriptsdir2\script1.c ...
  5. jefc

    "Can't find include file" error after upgrading to 2021.0

    Perhaps it would also help to be able to add the paths to .c files in the directive file as well, is that something that could be done?
  6. jefc

    "Can't find include file" error after upgrading to 2021.0

    Hello, After some additional tests with the provided C compiler, the following command seems to work with UNC paths if we add a pbcore.h header containing the declaration of the SetVar function used in our C script (we didn’t find any pbcore.h in the installation folder, so we assume it is...
  7. jefc

    "Can't find include file" error after upgrading to 2021.0

    In our project file, we are using the Call a C function custom action. Since this requires using absolute paths and since we cannot guarantee all developers use the same path for their code repositories, we put the C file (and identically named header) in a folder, thus using a UNC path in the...
  8. jefc

    PFXFile directive

    OK, thanks for confirming. Perhaps it would be nice to have a note about it in the documentation if it is not already the case (I couldn’t find it but perhaps I didn’t look in the right place).
  9. jefc

    PFXFile directive

    Hello, I noticed that the PFXFile directive documented in https://www.installpackbuilder.com/help/directives also serves as the certificate subject name when SignCertifLocation=1 or the certificate thumbprint when SignCertifLocation=2. I assume that this is because the 3 of them refer to the...
  10. jefc

    Feature Request: Extend registry access

    Hello, Would it be possible to extend the registry access (through CA and PB GUI) to be able to pass some registry options and access rights? This would allow accessing both 32-bit and 64-bit parts of the registry (which is currently documented as impossible) and also choosing if a registry key...
  11. jefc

    Warning when compiling x64 version of mainscript.c

    I’ve just sent it a couple of seconds ago.
  12. jefc

    Warning when compiling x64 version of mainscript.c

    Yes, sure. How should I send it to you?
  13. jefc

    Warning when compiling x64 version of mainscript.c

    Hello, When building x64 packages with Paquet Builder 2018.1, we observe the following warning when mainscript.c is compiled:
  14. jefc

    Uninst.exe not removed when run silently

    Hello, When uninstalling a package silently by executing “Uninst.exe /s” in a command prompt, all files are removed but the Uninst.exe file itself. If the “/s” flag is not used, the Uninst.exe file is removed during installation. PB version: 2018.1 Why this difference? It looks like the...
  15. jefc

    Shortcut customization hell

    Hello, do you have any news regarding this issue?
Back
Top