I've been trying to create and update an AIP (Admin install point). I've noticed that if I create and update my AIP in two separate command lines then it works fine but when I combine the two then it doesn't work.
For example:
A) This works fine:
1) msiexec /a <path to source MSI>
2) msiexec /a <path to MSI from AIP created in (1) above> /p <path to patch>

B) But the following doesn't work. An AIP is created but without an MSI while the MSI in the source installer folder gets modified:
1) msiexec /a <path to source MSI> /p <path to patch>

* Don't worry about the target directory, I'm setting it through the UI.

My question is that is option (B) above supported in windows installer.
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Have you tried swapping wheels on a car which isn't there? Attempting option B is the same thing - you're trying to patch a file which doesn't exist.
Answered 05/20/2011 by: VBScab
Red Belt

Please log in to comment
Isn't it similar to single transaction msiexec /i <path to source MSI> /p <path to patch> ?? What is the difference while installing the product and creating an AIP out of it. :(
I'm new to windows installer and am just trying to understand how it works. I couldn't find any documentation regarding this on MSDN and hence the confusion.

I would really appreciate your help.
Answered 05/20/2011 by: deployX
Orange Senior Belt

Please log in to comment
Creating an AIP extracts the files from the MSI's CABs - whether they're internal to the MSI or external and creates a new MSI with the Media table altered to reflect that. The bizarrely-named WordCount "property" which you'll find in the SUmmaryInformation stream is aso changed. It is the *new* MSI and the files it references which are then patched.
Answered 05/21/2011 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity