FLS
Posts: 29
Joined: Thu Jun 29, 2006 1:46 pm
Location: Nashville, Tennessee, U.S.A.

Problem With Patch Installation

I have an odd problem (don’t I always!) that I am hoping to get some help with.

I have created an application for the sole purpose of trying to figure out just how a patch works as I have several “real” applications where this would be very useful given the relatively large file sizes.

I created the .msp file, uploaded it, set up the .ini file for it and it works! Great!

Well – sort of. There’s a problem and I’m sure it’s something that I’ve either done incorrectly or not done properly.

When it installs, I then have two desktop shortcuts and in the program groups, I have two listings there also. They both point to exactly the same file though, and neither of the .msi files is set to allow “side-by-side installations”.

Any help here on where I went wrong would be greatly appreciated.

Thanks as always!
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi,

We are unable to reproduce this behavior. Are sure that you do exactly like in this tutorial:
http://www.advancedinstaller.com/user-g ... tml#create

If the problem persist the please send the AIP files of both .msi and .msp packages (if not contain any confidential information) or a test AIP files that reproduce this problem to support at advancedinstaller dot com.

Also please send a log file for the .msi and for the patch. You can obtain the log by running the package with "Run and Log" option from Advanced Installer or with the following command line:
msiexec /i package.msi /l*v log.txt

Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
FLS
Posts: 29
Joined: Thu Jun 29, 2006 1:46 pm
Location: Nashville, Tennessee, U.S.A.

I’ll be happy to send you guys the files, but before I do that, I suspect that if I explain the procedures that I took, it may explain where I went wrong. For clarity here, I’ll just use the terms “Version 1” and “Version 2” to make it easier.

I built Version 1 last week and have it and the .msi file saved. I have a new file to add, so with that, I set about to create the patch.

I opened the .aip file for Version 1 and did File >> Save As, and saved it as Version 2 (is this step where I went wrong perhaps?).

I next changed the version number to 1.1.0 and answered “No” to changing the product number. I then added the new file, changed the value in the registry, etc., saved again, then built the .msi file for Version 2.

I closed and then re-opened Advanced Installer and this time chose “Patch” and, using the wizard, stepped through everything and built the .msp file, and that’s where I am with things.

If you still want me to send you the files, just tell me who (or what to use for the subject line) to send it to.

Thanks as always!
FLS
Posts: 29
Joined: Thu Jun 29, 2006 1:46 pm
Location: Nashville, Tennessee, U.S.A.

Update:

Forget all of this.

I'm pretty sure I know where I went wrong, although I won't be able to test my theory until I have another update available which will be several days (possibly a week).

If the problem persists, I will report back.


Thanks
FLS
Posts: 29
Joined: Thu Jun 29, 2006 1:46 pm
Location: Nashville, Tennessee, U.S.A.

I did, indeed, find and correct my problem. I have now successfully created a patch and it works fine, but I do have some questions about the use, and that is with regard to the next version.

To simply things, let’s say I have Version 1, then Version 2 which is updated via a patch. As Version 3 is built, when I go to create the patch for it, which Version do I select as being the “old” one? Version 1 or Version 2?

I’m confused here no matter which is the case.

If I point it to Version 1, then it seems rather pointless since part of Version 3 patch will have been contained in Version 2, and at a certain point in time I may as well have just done a standard update rather than a patch.

If, on the other hand, I point to Version 2, then what happens when a new user comes along, downloads and installs the base version (Version 1), then updates it? It’s now missing Version 2.

Your guidance is appreciated.

Thanks!
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi,
To simply things, let’s say I have Version 1, then Version 2 which is updated via a patch. As Version 3 is built, when I go to create the patch for it, which Version do I select as being the “old” one? Version 1 or Version 2?
Patches are usually used for small upgrades between two consecutive versions (for example from version 1.1.1 to version 1.1.2). And the path should have a suggestive name (for ex: "patch_1.1.1_to_1.1.2.msp") this inform the user that needs version 1.1.1 to apply the patch.

For large upgrades (for example from version 1.1 to version 1.2) my recommendation is to use standard upgrades.

Hope this helps.

Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
FLS
Posts: 29
Joined: Thu Jun 29, 2006 1:46 pm
Location: Nashville, Tennessee, U.S.A.

Let me explain what it is that I am attempting to do and you tell me if a patch is appropriate here. Quite possibly I’m using the wrong method.

I have an application that allows the users to download and play videos (they are political commentaries lasting anywhere from three to sixteen minutes). The average size of each video is around 12 megs.

A new video is added every week, and I want to be able to give the user the ability to download the latest ‘version’ which will include that week’s show.

Using a patch, only the latest show is added; however using the standard full update method would mean that each week the .msi file will get progressively larger and larger.

Is this an inappropriate use for a patch?

My concern is that I cannot quite grasp what would happen if, say, someone were to miss one particular update (.msp), but instead jumped ahead to a later one. Would the use of prerequisites here be in order or …?

Thanks!
FLS
Posts: 29
Joined: Thu Jun 29, 2006 1:46 pm
Location: Nashville, Tennessee, U.S.A.

Update from my message of this morning:



I have figured out the answer to my question of this morning, and that is through the use of “Depends”. I like this feature!

It seems to work, but before I can really commit to the validity of that statement, I have a larger issue regarding patches that is the focus of this reply.

- - -

As I said earlier, what this whole thing does (per revision change) is this: My application is modified and a new file is added to a subfolder. Additionally, in the .msi file, the registry value of “Version” is changed to reflect that particular version. That’s really the extent of the whole thing.

I originally created version 1.0 (actually 1.0.0, but the trailing “0” is redundant for this prose).

On the first new revision, I created a true update by incrementing the version and answering “Yes” to generating a new product code. This then gave me version 1.1 and all worked fine.

Upon the next revision, I began to experiment with these patches. I created an .msi file for version 1.2 (answering “No” to generating a new product code), then created a patch for it. Again, all worked flawlessly.

On this latest addition, however, even though I followed the very same procedures to create version 1.3, the patch has failed to work, and for the life of me I cannot seem to figure out why!

With version 1.2 installed, running the .msp to update it to 1.3 does add the new file into the subfolder, but it fails to “update” the actual application. Oddly enough though, if I uninstall it then run the .msi for version 1.3 directly, it works!

Thinking that surely I must have botched up something in the process, I started again. I started with version 1.2, did File>>Save As, saved it as version 1.3, added my new file and updated the registry value, and built it.

I then created a patch pointing to version 1.3 as the new and version 1.2 as the old. Once again, it failed to work and I am completely stumped as to what I did wrong since I followed the very same procedure as I did to create version 1.2.

If you want me to send you the files (yes, I kept everything this time!), I’ll zip up the entire lot of the, upload it to my web server, and send you a link. Just tell me who to e-mail it to and/or what I need to put into the subject line.

Thanks again.
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi,

In order to investigate the problem could you please send both AIP files (1.2 and 1.3 versions) and AIP of the patch (if not contains confidential informations) to support at advancedinstaller dot com.

Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com

Return to “Common Problems”