Loading

Use

Skip Feed
  1. RegEx.dll from INNO/PASCAL to InstallScript

    I am converting some INNO/PASCAL code to InstallScript. A DLL, called RegEx.dll, is used in the INNO/PASCAL code to do regular expression replacements. Is there anyone familiar with the RegEx.dll used in INNO/PASCAL code and how to use it in InstallScript?


  2. How can I use the Flexera.FlxLicensingClient.core.2023.9.0 NuGet package on Linux arm64?

    Hi,

     

    I am using the Flexera.FlxLicensingClient.core.2023.9.0 NuGet package on Windows and Linux x64.

    Now, I want to use it on Linux arm64.

    In the NuGet file, there is no arm64 .so library included.

     

    How can I proceed here?

     

    Best regards

    Expand Post
    Question with a best answer.

    Best Answer

    Hi @Wolfster​ ,

     

    Support for Linux ARM64 in the .NET-XT Core SDK is slated for Q2 2026.

     

    Best regards,

    Jim

    Expand Post
    jberthold by jberthold (Flexera Software)

    1 of 2
    • Hi @jberthold (Flexera Software)​ 

       

      Thank you for the information that support for Linux ARM64 in the .NET-XT Core SDK is slated for Q2 2026.

       

      I would like to follow up and ask if you can already provide a more specific date in Q2 for the release of the NuGet package.

      If this information is not yet available, I would be grateful if you could let me know when a more precise timeline can be expected.

       

      Thanks for your help.

       

      Best regards

      Expand Post

  3. How do I access Path Variable Overrides values at runtime from within InstallScript?

    I am building an installscript project and attempting to use the same project with multiple releases. To help with that, I'm trying to override some Path Variables and Registry Path Variables at build time, so I don't have to rewrite as many variables in the script each time we build a new release. However, we need our script to do some custom checks based on these values, and I can't figure out how to access the variables within the script. Is it just not possible at all?

     

    For example, we have a "Distribution" value we want to add to the registry. For releases for the USA, I can set a Registry Path Variable "DISTRO" and override that with "USA" for the USA release and that's great. However, when doing an update, we want to make sure that the underlying install is "USA" and not some other country before we install the "USA" code.

     

    With InstallScript I can access and read the installed "Distribution" value in the registry before the update runs, but I can't figure out how to compare it to the <DISTRO> Registry Path Variable using InstallScript. I tried referring to it like <DISTRO> or DISTRO, but the code won't compile successfully. Is there any way to do this, or will I have to go back to hard coding release-specific variables in the script?

    Expand Post

  4. Question on Video for Configuring Minor Upgrades

    I have an Issue with the results I get when I create a Minor Upgrade.

     

    The video demonstration was great. I see a few things right off I want to change to follow your convention/methodology. Still, I use the Express Edition. The UI for which is radically different from the Premier edition. As is the result I get from the build.

     

    I have documented my experience that I am remediating. Before pursuing the matter further, I need to verify my version, the Express version, is capable of building a Minor Upgrade like I saw in the demonstration video.

     

    Thank you kindly.

    Expand Post

    • Revenera_Ian (Flexera)

      Hi @dishmann​,

       

      Thank you for your post.

       

      InstallShield Express Edition does not support minor upgrades, only major upgrades. You would need to upgrade to InstallShield Professional or Premier Edition to gain access to configuring minor upgrades.

       

      If you decide to configure a major upgrade in the InstallShield Express Edition, you'll need to increment the product version, generate a new product code, keep the same upgrade code as the previous version, and add then configure an upgrade path.

       

      If you need further assistance, we'll need a support case to track this issue. Could you please open a case with our Support Team, about this issue, by email at support@revenera.com or by phone at (877) 279-2853, as long as you have a valid, active, unexpired technical support contract (maintenance plan)?

       

      Please let us know if you have any questions or concerns. Thanks!

      Expand Post

End of Feed
4 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
5 Posts

Related Topics

    Loading
    Use