from the aip file. I guess those attributes were left when I was trying out multiple builds now I have only one build. I am including the files.MultiBuildValue="DefaultBuild: ...
from the aip file. I guess those attributes were left when I was trying out multiple builds now I have only one build. I am including the files.MultiBuildValue="DefaultBuild: ...
Code: Select all
[exec] Creating CAB file(s)... done.
[exec] Creating MSI database... done.
[exec] Inserting CAB file(s) into MSI...
[exec] Exception - Error calling Msi API: 161 Method: MsiRecordSetStream Table: _Streams.
[exec] Result: -536805276
Please note that it is not recommended to manually modify the .AIP. In this particular case the MultiBuildValue attribute you are mentioning is not added or removed based only on the number of builds you have defined in the Media Page. It also depends on other project settings. Can you please give us more details about the initial problem that lead you to manually modify the .AIP?In order to get one of the edits in my command line /exec to be effective I had to remove the attribute
Unfortunately, there isn't a known solution to this behavior. You could try reinstalling Windows Installer and see if it persists.I have been working in the GUI and switch to run an ANT command line build I get the following:I simply re-run the Ant build and it completes successfully.
If you run the same command file (aicommands.txt) though each of the two aip files I have provided (they differ only by removing the MultiBuildValue related to my properties). The resulting msi produce different results. The "Copy (4)" version produces a directory with the default name ("SVN0.0.0.0") under f:\products\nlbk whereas the "Copy (5)" produces the correct sub-directory as set by the command line /exec settings ("1.4.0.0").Can you please give us more details about the initial problem that lead you to manually modify the .AIP?
FOLLOW US
Get the latest news in Application Packaging