Avoiding multiple setup projects - 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!

markr002
Posts: 21
Joined: Mon Dec 20, 2010 5:38 pm

Avoiding multiple setup projects

Hello,

My primary setup project contains a .NET application that compiles to "Any CPU" (e.g. is both 32 and 64 bit compatible). For this reason, the setup package type is "Mixed 32/bit bit" (I'm using enterprise edition of AI). The setup project also defines prerequisites for downloading / installing the .NET Framework, as needed. Both of these setup features require use of the AI bootstrapper.

Now comes the problem I'm having. I also need to generate 32 and 64 bit MSI app packages (same files, etc.) that are GPO Deployment friendly. If I'm understanding correctly, this means that I can no longer use the mixed 32/64 bit package type, the enhanced UI themes, or the built-in prerequisites mechanism.

Are these assumptions correct? If so, is there any way I can avoid having three distinct setup packages in this scenario (one for the bootstrapped 32/64 bit mixed build with prerequisites and enhanced UI, plus two other "plain" ones - one each for 32 and 64 bit outputting GPO-friendly MSI packages)?

Please let me know if there's some other option I'm overlooking, and thanks.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Avoiding multiple setup projects

Hello,

Unfortunately all the features you mentioned:
  • global prerequisites
  • mixed 32/64 bit package type
  • enhanced ui
are not implemented by Windows Installer and need to use the Advanced Installer bootstrapper.

Since you cannot deploy an EXE through GPO you can try the following:
- you can launch the prerequisite with an "Attached Custom Action" under the "InstallExecuteSequence" -> "InstallFinalize" standard action in the Custom Actions menu page. You can show the "InstallFinalize" standard action by using the "Show Standard Action" toolbar button or context menu. Also set its execution property to "Asynchronous execution, do no wait for return".
- if you have the same files for both 32 and 64 bit packages, you can deploy only one 32 bit MSI that will install on 64 bit machines as well. The only issue here would be the install location but since everything will run I don't think this can be an issue.


Regards,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”