Advanced Installer Community

a_j_burgess

I have noticed a coupe of issues with the latest version of AI:

1. Not possible to store CAB outside of msi when building (even when it is selected)
2. Patching build behaves "differently". i.e. build process seems to be different and no instruction as to why it fails when

I luckily had a copy of ...

a_j_burgess

I tried to build using 4.2 instead of 4.6 and got the error 2771 when attempting to apply.

Is it possible to run a patch in debug mode (like using msiexec /l etc for msi files)?

If so, I can try to fix the problem myself and report back to the forum

Thanks

a_j_burgess

thanks Gigi. I shall tr this

a_j_burgess

Hi,

I have created two releases (msi's) for my application using the same .aip file (just some souce files are different between the two versions) to ensure consistency. The product version number is also the same so patching should be possible. However, when I try to build a patch, I get the ...

a_j_burgess

Hi,

I am using AI to install an application that is 250MB once installed. This is made of of many small files and takes a long time to build each release. We have now started to use the msp approach to patching and the process of building the "before" and "after" releases and then generating a very ...

a_j_burgess

Gigi,

Wow. A perfect answer! I usually ask really obscure questions on this site to which I get responses that I don't really understand.

Many thanks for both answers.

Regards,

Anthony

a_j_burgess

Hi,

There are a number of older versions of my application installed in various sites, whose msi was built using AI 2.2. I have recently upgraded to 3.9, which was not backwards compatible against 2.2 and, as a result had to built the aip from scratch, although using the same file structure, app ...

a_j_burgess

Hi,

Thanks for that. I checked the links that you provided and can confirm that the original file has equal creation and modification dates. Both of these dates are earlier than the creation date of the new file. This being the case, the original file should be overwritten. But it isn't.

I ...

a_j_burgess

Hi,

I have attached a fragment of the log file where you can see that the file 'InstallerScript.vbs' is replaced by the new one. The 'images\setup\' folder is where the upgraded version is stored and they must be difference or else the AI would not have flagged it:

---START LOG---
Building ...

a_j_burgess

Mihal,

The CAs are installed not attached (Type code 1174). The second version definitely does not run. Debug messages in the log, that only relate to first version confirms this. The 'disabled' parts are actually deleted from the new vbscript which means that, if the second version WAS run, they ...

a_j_burgess

Mihai,

thanks for the reply. The condition set on the original msi was 'NOT REMOVE~="ALL"' which I believe means that it will always run except when the product is being uninstalled. If this is not the case, is it possible to overwrite the condition with a patch?

The names of both the CA and the ...

a_j_burgess

I did not realise that this was the way the patching worked. That has made things a little clearer for me too.

However, my patch needs to modify one of the custom action scripts and then run it. I have tried to modify it in the 'upgraded' msi but the original script from 'target' runs. I also tried ...

a_j_burgess

Mihai.

Thanks for your post. Both of your possible faults refer to the value of TARGETDIR not being passed to the .vbs script. I don't think that this is the problem as I have been able to output the value of TARGETDIR within the .vbs:

Action start 14:05:17: InstallFinalize.
1: RunInstallScript ...

a_j_burgess

Hi,

I created a small test installer to narrow down the problem. The test file does (/ is supposed to do) the following:
Install two files - 1 is a .txt, 1 is a .vbs that attempts to read the .txt
Added custom action "InstallScriptProperty" to pass the install directory:
After standard action ...

a_j_burgess

Hi,

I built an installer that used deferred custom actions some time ago using version AI 2.2. I am now trying to upgrade to the latest version (3.3). However, the deferred actions do not seem to work in the same way.

I want to run a "File installed with the product" type of action after all of ...

Suggested Articles

User Guide

Videos

Refer & Save Up to 30% On Your Renewal

Search found 15 matches

4.6 installer inconsistencies

thanks

Build error when creating patches

Creating precompiled modules to speed up build and patching

Thanks

Requirements for detecting old versions

Altering custom actions in MSI with Patch

reply to Mihai

Update..test install

Deferred Custom Actions are not deferred in version 3.3

Caphyon Products

Company

Product

Resources

Free Tools

Connect

Community