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!

blaze
Posts: 16
Joined: Wed May 23, 2007 7:16 pm
Location: Macrovision
Contact: Website

Build All behavior change

When using AI Enterprise 4.x, I had defined two Media rules. The default rule builds an executable and a secondary rule builds an msi file for patch construction. At the time I could select the Build button, both builds would run and the result would be both exe and msi files. I am not certain when the behavior changed, but I am currently using AI Enterprise 6.2. When I perform a general build both media types compile, but the second media type does not result in the generation of a msi file in the target directory. Building the second media type explicitly does work.

Code: Select all

[ DefaultBuild ]
Building package (en): C:\cygwin_blaze\dev1\TES8_Encoder\TES8_Install\Release\TES8_Framework_Installer.9.0.1.exe 
Reusing archives from cache... done.
Creating MSI database... done.
Writing Summary Information... done.
Adding merge modules... done.
Creating EXE file... done.
Creating Autorun launcher... done.
Build time: 7 sec.

[ MsiBuild ]
Building package (en): C:\cygwin_blaze\dev1\TES8_Encoder\TES8_Install\Release\TES8_Framework_Installer.9.0.1.msi 
Reusing archives from cache... done.
Creating MSI database... done.
Inserting CAB file into MSI... done.
Writing Summary Information... done.
Adding merge modules... done.
Creating Autorun launcher... done.
Build time: 4 sec.

Total build time: 11 sec.
Build finished successfully.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Build All behavior change

Hi,
When I perform a general build both media types compile, but the second media type does not result in the generation of a msi file in the target directory.
I'm not sure how you configured the builds. Can you please send us the AIP to support at advancedinstaller dot com so we can investigate it?

The build log you pasted shows that the packages were built correctly. Note that if the build contains a bootstrapper, the build log will not show the path of the MSI file, it will show only the path of the EXE file. Also, the "Build" button builds only the project which is shown with bold letters in it's options menu (click the small arrow next to the button).

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
blaze
Posts: 16
Joined: Wed May 23, 2007 7:16 pm
Location: Macrovision
Contact: Website

Re: Build All behavior change

Just to close the topic; Cosmin explained that the building behavior did change to add a build caching feature.
Basically, Advanced Installer will clean-up the build folder after all the builds are generated (instead of cleaning up
after each build). Since the first MSI file is included in the EXE and the second MSI file has the same name as the
first one, Advanced Installer will remove the second MSI because it considers it has been included in the EXE.

The advantage of this method is that the build process uses the cache and the build is faster. However, you cannot have
two builds which generate files with the same name in the same folder.
So now I understand why the behavior changed and I have adjusted my media target to adapt.
Thank you!

Return to “Common Problems”