Patching Web Media

Got a problem you cannot solve? Try here.
Post Reply
paul.fitzpatrick@avondata
Posts: 34
Joined: Wed Sep 09, 2009 9:08 am

Patching Web Media

Post by paul.fitzpatrick@avondata »

I have followed the Patching white paper, but when I choose to build my patch I get this message. How can I resolve it?

Error during build: At least one Web Media Block must be defined before installation commands that may require media


Thanks
paul.fitzpatrick@avondata
Posts: 34
Joined: Wed Sep 09, 2009 9:08 am

Path Web Media Error

Post by paul.fitzpatrick@avondata »

OK, am not sure if I have done this correct, although I have got round the last error by putting [OFFLINE CONTENT] at the top of the MSI Script.

I now get this error:

Error during build: No compatible base packages found for upgrade package

I am referencing the original installation Web Depolyed EXE.

Any help out there?
Thankyou
MichaelNesmith
Posts: 3452
Joined: Thu Dec 22, 2005 7:17 pm
Contact:

Post by MichaelNesmith »

Do the upgrade GUIDs and package GUIDs match?
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
paul.fitzpatrick@avondata
Posts: 34
Joined: Wed Sep 09, 2009 9:08 am

Post by paul.fitzpatrick@avondata »

Yes they do; just to confirm the GUID that need to be the same between original base setup and patch are:

Product Code
Revision Code

In the Project Properties page.

In fact, it is the same project, I have simply replaced a couple of files, added some new, Rebuilt the Web Media Blocks, add the patch reference to the project (which is from the original build) and then click Patch.
MichaelNesmith
Posts: 3452
Joined: Thu Dec 22, 2005 7:17 pm
Contact:

Post by MichaelNesmith »

Is the revision code not changing maybe? Is the version number changed?
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
paul.fitzpatrick@avondata
Posts: 34
Joined: Wed Sep 09, 2009 9:08 am

Post by paul.fitzpatrick@avondata »

I don't think the revision code changes from build to build - should it? If so, can I manually change it? Also the version number is the same as before (1.0). Should I change this?
MichaelNesmith
Posts: 3452
Joined: Thu Dec 22, 2005 7:17 pm
Contact:

Post by MichaelNesmith »

The version number should change, so should the revision code (it is set to auto-change unless you turned it off explicitly). Whitepaper errata...
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
paul.fitzpatrick@avondata
Posts: 34
Joined: Wed Sep 09, 2009 9:08 am

Post by paul.fitzpatrick@avondata »

Have you got a link to the White paper in question. And, where us the option to turn the options on/off - I can then go and make sure it's on
MichaelNesmith
Posts: 3452
Joined: Thu Dec 22, 2005 7:17 pm
Contact:

Post by MichaelNesmith »

Project Options dialog. Meant to say, its an omission in the whitepaper.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
paul.fitzpatrick@avondata
Posts: 34
Joined: Wed Sep 09, 2009 9:08 am

Post by paul.fitzpatrick@avondata »

OK, I have tried what you suggested, The option was already selected, and the revision code does automatically change each build, the version number did not change though. I manually changed the version number though.

I get the same message as before though:

Error during build: No compatible base packages found for upgrade package

If I change the base package to a non Web Block and rebuild all is OK - I cannot do this though as my base installation which is installed across many many sites uses the Web Block which I must be able to patch.
paul.fitzpatrick@avondata
Posts: 34
Joined: Wed Sep 09, 2009 9:08 am

PROBLEM FOUND

Post by paul.fitzpatrick@avondata »

I have found what the problem is! It is because I have specified a password on original base installer, I created a small test IA Project, and produced a Web Depolyed project with a password, on attempting to perform a patch I get the same message. If I rebuild the web deployed project with a password and create a patch - It works.

This leaves me with potentially a BIG problem. If I rebuild my project again now without a password, will the patch I create against it work for all my customers who have already installed my base installer???
Post Reply