Patching - Remove Options for version # to use

[bhawkins]

Hello,

We have successfully build installs and patches for multiple versions .... not a major upgrade. The versions are: 4.0.1; 4.0.2 and 4.0.3.

When building the Updater.aip we have these defined as Replaces (pseudo screen shot

Product Name 4.0.3
>>> Replaces
>>>>>>> Product Name 4.0.2
>>>>>>>>Product Name 4.0.1

Product Name 4.0.2
Product Name 4.0.1

So, if 4.0.1 is installed, when updating; User is given options to update 4.0.3 or 4.0.2 - with 4.0.3 being the default.

For a development tool I can understand having this feature as I may wish a very specific version not the latest (this is cool feature).

However, for our application we wish to just allow the user to actually only have option to update to the latest version. Is this possible?

Cheers,
Bruce

[Bogdan]

Hi Bruce,

Currently Advanced Installer doesn't allow you to create such a scenario.

You can use your current scenario, recommended, which will not allow to user to select multiple versions, so they can only install one of them. Since the latest will be checked by default I see no reason for an user to select an older version.

Regards,
Bogdan

[bhawkins]

Bogdan,

Since this is not possible, we can live with it. Having options for end users always results in confusion for them. In our case there is no advantage to them not going to the latest version.

I will put this forth as a suggestion for future versions

Thanks for the response,
Cheers,
Bruce

[bhawkins]

Hello Bogdan,

Been thinking that maybe I can actually just not include the intermediate versions in the Updater aip.

Start out with 4.0.1 .. then 4.0.2

When 4.0.3 comes out .. just replace the 4.0.2 with 4.0.3 .. then there is no 4.0.2 in the list.

I am imagining any client with 4.0.2 will still be able to update even it is not in the list.

Would this work?

Now we would just have to keep all the update Features, Enhancements and Bug Fixes and accumulate them in the one Update (latest) if we wish to have a complete list of the changes.

I am wanting to do this only for the new release of a new product for the first month as likely there were be many small changes required. I do not wish to have all these in the list. Once things stabilize then we can have regular scheduled patches.

Thanks,
Bruce

[mihai.petcu]

Hi Bruce,

Would this work?

Yes it would. By adding multiple targets to a patch it can update multiple versions of your application.

Now we would just have to keep all the update Features, Enhancements and Bug Fixes and accumulate them in the one Update (latest) if we wish to have a complete list of the changes.

By definition and design patches should contain small updates. If you have several modifications you should have a major upgrade instead. Here's the Creating Patches user guide article that explains this.

All the best,
Mihai