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!

Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Registry Search - Conditional Install - Issue

Hello,

In order to achieve what you want you can proceed like this:
- Go to "Install Parameters" page and add a property like this:
  • Name: GOLD_UR
    Value: C:\XPS\PARM
- Go to "Files and Folders" page and create a property-based folder using the above property.
- Under the above property-based folder create 4 sub-folders (10_DYNAKEY_ALL, 20_TOUCH_BC, 30_TOUCH_UR and 40_GOLD_BC) having the "Install folder content into the parent folder" option enabled.
- Go to "Organization" page, and for all components of the files from GOLD_UR folder add the following condition (in the "Condition" field from "Component Properties" right pane):

Code: Select all

Config_Type = "BC" OR Config_Type = "UR"
- For all the components of the files from 40_GOLD_BC folder add the following condition:

Code: Select all

Config_Type = "BC"
- For all the components of the files from 30_TOUCH_UR folder add the following condition:

Code: Select all

Hardware_Type = "TOUCH" AND Config_Type = "UR"
- For all the components of the files from 20_TOUCH_BC folder add the following condition:

Code: Select all

Hardware_Type = "TOUCH" AND Config_Type = "BC"
- For all the components of the files from 10_DYNAKEY_ALL folder add the following condition:

Code: Select all

Hardware_Type = "DYNAKEY"
- Build and run your project.
Punch Registry with the installer version number - doesn't need to be installed under program files or in the control panel under programs. Thoughts on how this can be done?
In order to achieve this you should not add any resource files in folders, from "Files and Folders" page, which will be resolved to "Program Files" at installation time. Also, you should enable the "Do not show in list" option from "Product Details" page.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
dsc
Posts: 14
Joined: Fri Mar 29, 2013 3:01 pm

Re: Registry Search - Conditional Install - Issue

Hi Daniel,
I followed the instructions below but the conditional logic doesn't appear to be working. Attached is the installer log that shows the files being copied to C:\XPS\PARM but not taking into consideration the conditional logic setup within the Organization section. Any thoughts?

Thanks
Attachments
Installer_log.txt
(189.37 KiB) Downloaded 353 times
dsc
Posts: 14
Joined: Fri Mar 29, 2013 3:01 pm

Re: Registry Search - Conditional Install - Issue

Bumping this up for review.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Registry Search - Conditional Install - Issue

Hello,

Can you please send us the .AIP (project file) to support at advancedinstaller dot com so we can investigate? Also, can you please specify what is the installation result you expect to achieve?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
dsc
Posts: 14
Joined: Fri Mar 29, 2013 3:01 pm

Re: Registry Search - Conditional Install - Issue

Hey Daniel,
I've sent the .aip file to the support email and the expected results are based off of the requirements previously provided.

Thanks
dsc
Posts: 14
Joined: Fri Mar 29, 2013 3:01 pm

Re: Registry Search - Conditional Install - Issue

Bumping this up for review.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Registry Search - Conditional Install - Issue

Hello Derek,

I've sent you a reply to your e-mail address yesterday. Can you please send us a verbose log created with the EXE package built with the last sent .aip file to support at advancedinstaller dot com? It seems that the last log file attached here is created with another installation package. In the related log file appear different components name (e.g. tc2_12, tc2_13, GOLD_BC) which I can't find in your current .aip file. Also, can you mention which file is installed on target machine besides it shouldn't?

Also, I've tested a similar scenario, but I cannot reproduce the behavior. Can you test again your installation package and see if the behavior still reproduces?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”