Procedure Advice - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

td80401
Posts: 1
Joined: Mon Apr 19, 2010 6:29 pm

Procedure Advice

My marketing department is always coming to us with these html "applications" (bunch of .html pages with asset folders as sub folders). We build them a a V1 MSI. A few weeks later they come to us with change files - either .html page additions, additional assets, etc., so we build a V2 MSI.

Now, some of the end-users come back and say they did not want to re-install a whole new application, just the updates.

What is the best approach to take here - update, patch, ??? - without any server interaction or coding, if at all possible. I don't want to create a new large task load for myself, but understand the desired end-result.

The versioned application has zero external interaction, just inter-linked html files and assets.

TIA.
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Procedure Advice

Hi,

A patch should work very well for deploying your updates, this way the users will receive only a package
that contains the changes from the new version, not the entire new package.

Here is a tutorial written by us on how you can create a patch, please follow it carefully, especially the patch rules.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”