Announcement

Collapse
No announcement yet.

Trial User here evaluating the software. Have some initial questions.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Trial User here evaluating the software. Have some initial questions.

    I just downloaded the software and was happy to see that it produces x64 installer files (as in the exe is actually x64 and not just "compatible with x64 os).

    I've got a unique situation where many of our customers use wine to run our software on mac/linux. MacOS Catalina was recently released and no longer runs 32bit software so our users cannot install our software on Catalina. There are very few installer software packages available that produce x64 binaries so I'm hopeful this one will fulfill the rest of our needs as well and we can make the switch.

    For the most part, other than x64, our installer needs are pretty simple and standard (Start menu/desktop shortcuts/registry entries/etc). However, brief searches (remember I just found this software today) haven't turned up a couple things we need.

    1) Can I automate (or even script) building the installer? For example, can I run
    Code:
    SUFDesign.exe /build MyProject.suf
    and produce an installer that can be distributed to customers? Is it possible to edit .suf files using scripting external to the SUFDesign.exe UI?

    2) Does the app support EV Code Signing certs (with the hardware dongle)? I see where it does signing using a cert file. However, when signing using a dongle, you don't specify a file. Looking at this post: https://forums.indigorose.com/forum/...023#post304023 It looks like I shouldn't have any issues since we already do our signing with a batch file using our current installer. Does this sign all signable files in the build? Or just the installer itself. Does it sign the uninstaller that is produced?

    3) Can I execute a function from a system DLL (NTDLL.dll) and then do conditional logic based on the results of that function call? Would this be possible from the scripting capabilities (I really haven't explored this feature at all yet).

    4) Update Environment variables (system preferably but user is ok). We add our software to the PATH environment variable to make it easier to launch.

    5) Purchasing. We only have a single developer that will handle creating/managing/modifying the installer environment. But as mentioned above, we do have an automated build process that is triggered anytime ANY developer pushes code to source control. Is a single seat sufficient or do we need an extra seat for the build machine?

    6) Purchasing. I see that the purchase comes with 6mo Support & Maintenance. However, I don't see a price for continued support/maintenance. Is this an option? Or would we simply be required to purchase any new versions when they come out after the 6mo period?

    Thanks

  • #2
    1) Can I automate (or even script) building the installer? For example, can I run
    Code:
    SUFDesign.exe /build MyProject.suf
    and produce an installer that can be distributed to customers? Is it possible to edit .suf files using scripting external to the SUFDesign.exe UI?
    Hello,

    Yes, you can build from the command line. The arguments can be found in the product documentation as "Unattended Build Options":
    https://www.indigorose.com/webhelp/s...ne_Options.htm

    While you can edit the project file (it is an XML file), I suggest that you refrain from doing so, as I have seen customers breaking their files. You can use build constants, build configurations, ini files to allow you building several setups from a single project file - there should be no need to make any changes manually.

    2) Does the app support EV Code Signing certs (with the hardware dongle)? I see where it does signing using a cert file. However, when signing using a dongle, you don't specify a file. Looking at this post: https://forums.indigorose.com/forum/...023#post304023 It looks like I shouldn't have any issues since we already do our signing with a batch file using our current installer. Does this sign all signable files in the build? Or just the installer itself. Does it sign the uninstaller that is produced?
    There is no built-in support for EV code signing, but the forum post you found has a workaround. The batch file will be called for each executable - the runtime, the uninstaller, and the self-extractor.

    3) Can I execute a function from a system DLL (NTDLL.dll) and then do conditional logic based on the results of that function call? Would this be possible from the scripting capabilities (I really haven't explored this feature at all yet).
    You can bundle files with your installer, they are known as "Primer Files". Files added as Primer will be decompressed into the TEMP folder at runtime, and can be used in scripts before the product itself is installed. You can call also call DLLs and programs if they are already present on the target system, check for exit codes, and control the behavior of your script accordingly.

    4) Update Environment variables (system preferably but user is ok). We add our software to the PATH environment variable to make it easier to launch.
    While you can read environment variables, there is nothing ready for use to set or change a environment variable. Typically you would make the change in the registry, and let the system know that it was updated. ( Example )

    5) Purchasing. We only have a single developer that will handle creating/managing/modifying the installer environment. But as mentioned above, we do have an automated build process that is triggered anytime ANY developer pushes code to source control. Is a single seat sufficient or do we need an extra seat for the build machine?
    Our licensing model follows the "named user" method, where everyone who uses the product needs a license. Each individual can install the software on multiple computers (like a desktop and a portable). If you have a team up to five developers who run Setup Factory on their own or a shared computer (such as a build server), a five developer license (a "Team Pack") would be your best option, as it incorporates a significant discount.

    6) Purchasing. I see that the purchase comes with 6mo Support & Maintenance. However, I don't see a price for continued support/maintenance. Is this an option? Or would we simply be required to purchase any new versions when they come out after the 6mo period?
    Once you have a license, you can log into the Customer Portal. It is there where you can submit technical support requests, and renew the product maintenance and support, if desired. The product will not stop working once maintenance and support expires, and it can be renewed only when you need. You can also post questions here, of course.

    Ulrich
    Last edited by Ulrich; 12-20-2019, 09:25 AM. Reason: Clarified the licensing terms

    Comment

    Working...
    X