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!

Search found 4 matches

Go to advanced search

by eu_neke
Fri Aug 17, 2012 12:51 am
Forum: Building Installers
Topic: Conditionally include files and features in MSI?
Replies: 3
Views: 15730
 
Jump to post

Re: Conditionally include files and features in MSI?

After you build your complete installer, you can simply delete the CABs you don't want.
This would be great, except that we don't have the files to make the CABs from, and we'd prefer to have the whole thing in one file.

Also, is it possible to add/remove/modify launch conditions from the ...
by eu_neke
Thu Aug 16, 2012 2:27 am
Forum: Building Installers
Topic: Conditionally include files and features in MSI?
Replies: 3
Views: 15730
 
Jump to post

Re: Conditionally include files and features in MSI?

Also, is it possible to add/remove/modify launch conditions from the command line? The older versions that we support require .NET 2, but the newer ones require .NET 4.
by eu_neke
Thu Aug 16, 2012 1:35 am
Forum: Building Installers
Topic: Conditionally include files and features in MSI?
Replies: 3
Views: 15730
 
Jump to post

Conditionally include files and features in MSI?

I'm building installers for a collection of addons for an existing product. I need to build a separate installer for each version of the existing product, but I want to be able to use a single "template" .aip for all of them. The only issue is that not all of the addons exist for earlier versions of ...
by eu_neke
Thu Aug 09, 2012 6:27 am
Forum: Common Problems
Topic: Registry searches in mixed 32/64 installers change paths
Replies: 5
Views: 5041
 
Jump to post

Registry searches in mixed 32/64 installers change paths

I'm building a mixed 32/64-bit installer which does registry searches to find the location of an existing product.

I have two searches set to "Search the 64-bit portion of the registry":

One value contains the path to the 32-bit components of the existing product, which is usually something like ...

Go to advanced search