No announcement yet.

Dynamic package list

  • Filter
  • Time
  • Show
Clear All
new posts

  • Dynamic package list


    I'm using Setup Factory to install a Visual Studio 2019 extension.

    On startup, the setup locates all valid instances of VS2019 currently installed on the target and those instances are the ones that should be presented to the user via the select package dialog, where the user chooses which ones to install the extension on.

    The number of installed VS2019 instances can vary and it is impossible to predict, until during install time, how many they are and what their names are. As an example, you can have Community, Professional and Enterprise and then you can have multiple instances of each one.

    My fist thought was to define some maximum number of Setup Factory packages, then dynamically construct the names and availability during installation startup. A pretty safe maximum number would be, say 20.

    This approach actually fails as I can only disable packages, not hide them.

    Is there any option to hide and unhide packages during setup time ?

    Is there any option to dynamically add new packages at setup time ?

    If neither above is possible, I assume that my approach would be to use a List Box control to accomplish the above, right ?


  • #2
    I've been able to implement this using CheckBoxes, since they can be hidden and the dialog allows up to 20 checkboxes.

    I sure would like to know though, if dynamic packages or hiding of packages is possible.



    • #3
      What you describe is not what the packages in Setup Factory were designed for. Packages are groups of files. Any file can be part of multiple packages, if needed. You are attempting to create something different where this concept does not fit well.

      While it is technically possible to install Visual Studio 2019 Community and Visual Studio 2019 Professional or Visual Studio 2019 Enterprise side by side on the same PC, I am not sure if this is a common practice. If there are indeed multiple instances, then a "Check Boxes" screen could be shown to allow the selection of the desired target(s). If there is only a single development platform on the target PC, then this screen should be skipped.



      • #4
        Thanks Ulrich,

        Multiple editions may not be common practice, but since it is possible, I have to account for it. I do think it is quite common though, for instance I presently have Professional installed and then a Community edition preview for upcoming version.

        In any case, thanks for confirming that Packages can't be used.