Predefined Prerequisites via CLI

[swissphone_alex]

Hello,

We are using Enterprise license and Predefined Prerequisites feature to install two .NET packages during MSI installation. The functionality works well, but the problems start when we started to build a project with Predefined Prerequisites feature as part of CI (Continuous Integration) process using Advanced Installer CLI.

As I understood correctly, Predefined Prerequisites work like the following: when I check one of the predefined prerequisite, it asks "download prerequisite and include in package?" and In our business use case this question requires to answer "Yes" for offline mode. After that, .NET package appears on a local disk on the machine where the checkbox was set.

But if we build as part of CI process in distributed way (on different machines), .NET packages do not exist if the checkbox was set on another machine. As I see, the only option to download .NET installers is to uncheck and check the package checkbox of required predefined prerequisites again on the machine where the project builds. I couldn't find a way to interact with Predefined Prerequisites feature via CLI, only via GUI.

In other words, our goal is to do the same steps as here (https://www.advancedinstaller.com/net-f ... stall.html) by answering "Yes" (offline mode), but using CLI.

Questions:
1) Is it possible to enable/disable predefined prerequisite package via CLI?
2) If no, are there any recommendations how to tackle this situation?
3) Is it possible to download predefined prerequisite during project building somehow?
4) Or the only option for offline mode for predefined prerequisites is to store artifacts somewhere in remote storage and download before building a project?

Thanks!

[Liviu]

Hello and welcome to our forums,

I am afraid that once a prerequisite has been added using the online or offline options, it cannot be changed afterwards, for example by downloading the prerequisite later.

The /NewPrerequisite command is equivalent to the UI option "New..". With this option you cannot add predefined prerequisites.

The only solution in your case will be to have the prerequisites packages available on disk, as you mentioned in step 4. Then you can use the /UpdatePrerequisite command to update the prerequisites path.

Hope this helps! Let us know if you have any questions.

Best regards,
Liviu

[swissphone_alex]

Thank you for a quick response!
The current situation is clear.
We will proceed with point 4 then.

But it would be great in the future to interact with Predefined Prerequisites via CLI

[Liviu]

You're very welcome!

I appreciate your feedback. I'll pass this suggestion along to our team and hopefully an improvement will be added in a future version.

Let me know if you need any further assistance!

Best regards,
Liviu