Keep previously installed files no longer part of install - 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!

ariaudo
Posts: 3
Joined: Sun Sep 05, 2010 4:24 pm

Keep previously installed files no longer part of install

How can I create an updated install that does not delete files that were in the original install but are no longer present?

I want to create an upgrade install that only includes files that have changed since the previous release. This is to provide the smallest possible file for our users to download. The original installer comes on a CD and includes lots of additional files that rarely change - e.g. documentation, data, etc.

I'm using the freeware version of Advanced Installer.
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Keep previously installed files no longer part of install

Hello and welcome to Advanced Installer forums,

What you are looking for is a patch. Patches only contain resources that have changed since the last version.
Your can read up on patches from our user guide on patch projects.
Please note that patch projects are available for Enterprise users only.

I hope this helps,
Best regards,
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
ariaudo
Posts: 3
Joined: Sun Sep 05, 2010 4:24 pm

Re: Keep previously installed files no longer part of install

I guessed that the Freeware version did not have this functionality.

The Enterprise version is a bit over the top for my needs. This is a one man band operation here. Is there no way that updates created through the Professional version can be configured to leave specific files created in the original install alone, even if they are not part of the new release??
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Keep previously installed files no longer part of install

Hello,

It is theoretically possible to achieve the same effect in a Professional project, mind you it's not the recommended (or the 'right') way to do it.
Let's say you have the following structure:

Code: Select all

- first time install installs:
   - application.exe
   - file1.txt
   - file2.txt
   - file3.txt
- then you update your application to version 1.1 and the changed files were application.exe and file2.exe in that version.
Your 'update installer' (if we can call it that) backs up application.exe and file2.txt in the already installed application (using a custom action you will have to create), then installs the updated application.exe and file2.exe. But the update installer must be seen by Windows Installer as a totally new and separate product for this to work (new Upgrade Code and new Product Code). You can then uninstall the update and the 'update installer' should remove the application.exe and file2.exe automatically, then restore the backed up application.exe and file2.txt through some custom action.

But it's not a pretty workaround, and you must account for the case where the user uninstalls the main installation after the update has been installed. What should happen with the update in that case? Should it be uninstalled too?

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
ariaudo
Posts: 3
Joined: Sun Sep 05, 2010 4:24 pm

Re: Keep previously installed files no longer part of install

You're right - not very pretty at all.

With the Professional version, can the initial setup installation process be broken up into discrete stages, with seperate update installers for each stage? I was wondering whether I could have the core application files as one stage and the supporting data/documentation as a seperate stage, but all contained in a single installer for the original setup. If that is possible, could application updates then be dealt with in isolation utilising a small sized installer more suitable to easy downloads? Any changes to the much larger set of data/documentation that happen extremely rarely could then be dealt with seperately.

I may need to reappraise how I go about the whole installation process and how I can avoid the situation occuring where any of this is necessary.

Return to “Common Problems”