BCh
Posts: 63
Joined: Wed Jan 17, 2007 6:32 am
Location: Australia

Two Component Installs Linked - Program & Data

Hi,

Trying to get my mind around whether I can do the following.

I have to install and update a system that has a program component (~6MB) and a data component (currently 92MB).

At the moment I have been updating both at the same time using a single version control - ie if I get data updates then install program (even though no change) - or if update / patch program then also install all the data.

Is there any way to have a two version process - one for program and an other for data - or do I need to have two separate installations (not something I believe users would be able to handle)?

Or might I have to manage version control such that the second series of number points to program version and third series of number points to data version - for example.
1.1.100.0 = program version of 1 - data version of 100
1.1.101.0 = program version of 1 - data version of 101
1.2.1.0 = new program and new data
in this case program and data also get updated.

Is there a way I can:
1) Install both (program and data) for a new installation (OK with this) as well as...
2) Install only data component over an earlier version of program and data (keeping same program)....
3) Install both program and data over earlier version (as per current)..
4) Install only program (as a patch / enhancement).

I am looking at feasibility of updating off the web where client program would go looking for a file that contains updated data, download and then run a program to update data tables with new information - this would reduce 92mb to probably < 1mb for each update.

Any comments welcomed if you think there is a better way. At the moment we are creating many CD's and using snail mail to get the updates out which is costly and time consuming.


Thanks.
Brian.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi Brian,

For upgrading an installation you have two possibilities:
1) you use a patch
2) you use the automated upgrade feature

1) A patch project is basically the difference between two MSI packages (which makes it very small) and you can use it to update an installation. You can read more about patches here:
http://www.advancedinstaller.com/user-g ... oject.html
http://www.advancedinstaller.com/user-g ... tches.html
http://www.advancedinstaller.com/user-g ... patch.html

2) The automated upgrade feature works like this:
- you install a MSI on the target machine,
- you increase it's version and update some of it's files
- you answer "Yes" when changing the Product Code
- when running the updated MSI on the target machine the old installation will be removed and the updated package will be installed

For your situation I recommend that you use a patch because it has a small size and it updates the necessary files.

Please note that both method can be used by the Auto Updater feature. You can read more about this feature here:
http://www.advancedinstaller.com/user-g ... dater.html
http://www.advancedinstaller.com/user-g ... dater.html
http://www.advancedinstaller.com/user-g ... oject.html
Is there any way to have a two version process - one for program and an other for data - or do I need to have two separate installations (not something I believe users would be able to handle)?
You don't have to do this because only the files that you update in your project will be modified on the target machine.

Let me know if you encounter any problems.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”