Had to remove attributes in aip file - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

MikeMurnane
Posts: 30
Joined: Wed Dec 08, 2010 5:46 pm

Had to remove attributes in aip file

In order to get one of the edits in my command line /exec to be effective I had to remove the attribute
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.
Attachments
Copy (4) of ApplicationType01.aip
the one with MultiBuildValue attributes.
(15.27 KiB) Downloaded 312 times
Copy (5) of ApplicationType01(works).aip
works
(14.76 KiB) Downloaded 280 times
aicommands.txt
The command file - note the multiple GetProperty commands were my attempts to see what was happening (other forum post: GetProperty return no information)
(597 Bytes) Downloaded 304 times
MikeMurnane
Posts: 30
Joined: Wed Dec 08, 2010 5:46 pm

Re: Had to remove attributes in aip file

I have run into a relate issue (well, maybe not directly related I can't tell) ... sometimes, if I have been working in the GUI and switch to run an ANT command line build I get the following:

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
I simply re-run the Ant build and it completes successfully.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Had to remove attributes in aip file

Hello,
In order to get one of the edits in my command line /exec to be effective I had to remove the attribute
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?

The GetProperty bug is fixed and will be available in the 8.1.2 release which will be very soon.
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.
Unfortunately, there isn't a known solution to this behavior. You could try reinstalling Windows Installer and see if it persists.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
MikeMurnane
Posts: 30
Joined: Wed Dec 08, 2010 5:46 pm

Re: Had to remove attributes in aip file

I understand that I should not directly edit the aip file ... it was may last option to get the command line build to work.
Can you please give us more details about the initial problem that lead you to manually modify the .AIP?
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").

Note: Both runs have the same console feedback. Only with MultiBuildValue removed could I get the correct behavior and I saw no way to get the GUI to remove the attribute.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Had to remove attributes in aip file

Hello,

The behavior you are mentioning seems to occur because the property values for the DefaultBuild are not correct( appended backslashes to folder paths as opposed to none ). I have discussed this issue with the development team and we will improve the GUI so the user can edit the per-build value of a property at any time.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”