OPen Web Page AFTER install if prerequisite is not met - 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!

dotnetdude
Posts: 4
Joined: Wed Oct 08, 2008 6:47 am

OPen Web Page AFTER install if prerequisite is not met

Hi,

We would like to open a web page AFTER the main install is complete if a specific prerequisite is not met (in this instance a specific file in a specific folder). We can open the page BEFORE the install but this then loses the focus of the main install dialog and the user has to go hunting for it afterwards. The "Chain prerequisite installation after main package" is not allowed here it seems.

We would like to invoke the web page at the end which then provides details of what the user should do next (obviously this additional component is not critical to the actual installation process).

Many thanks for any help.

James.
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: OPen Web Page AFTER install if prerequisite is not met

Hi James,

You can do the following to achieve this:
- create a "Launch File or Open URL" custom action to launch the url.
- place it either under InstallExecuteSequence->InstallFinalize or under InstallUISequence depending on whether you want it to open when the installation completed or when the user pressed "Finish". You may prefer the second case, since it only launches the web page only when the install is not done silently.
- for the first case nothing more needs to be done, just make sure you properly condition the custom action
- for the second case you will need to add a DoAction control event on the ExitDialog's Finish button. Instruct the DoAction event to launch your UI custom action. Make sure you condition the event if needed.

Your request specifies that the URL should be opened only if a specific file is found on the system. Use a Search to search for the file. The result of the search is stored in a property. Use that property to condition your custom action or its control event depending on how you chose to implement it.

You can always refer to our user guide should there be any unfamiliar terms used in my explanation. Do let me know if there are things not documented that need clarification and I will be happy to assist.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
dotnetdude
Posts: 4
Joined: Wed Oct 08, 2008 6:47 am

Re: OPen Web Page AFTER install if prerequisite is not met

Hi Gabriel,

Thank you for your reply.

We were heading in that direction already but it's nice to have our steps endorsed.

One area we seem to be struggling with is the search condition result. We would like this custom action to be performed if a specific (third party) file is NOT installed on the system but we have tried a number of different conditions to test this without success.

We have a custom search which looks for eg. app.exe with the result in property IS_INSTALLED. When we "test" this within the search page is either shows "1: c:\......" or "1: " depending on whether it's installed or not - all this is great but...when we then try and use this within the "Execution Condition, Expression" we are unsure of what exactly to test for ie. "Not defined", "Defined" or for a value. Our first guess was to use the test of "NOT IS_INSTALLED" but this didnt work so then we tried the expression 'IS_INSTALLED = " "' but this didnt work, nor did 'IS_INSTALLED = "1: "'.

Could you clarify exactly what the expression should be when trying to determine if the file is NOT installed (I dont want to test if it IS installed as that would mean i need to be explicit for the drive lettering eg. "c:\program files\ etc etc" which I cannot allow).

Thanks again in advance.

James.
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: OPen Web Page AFTER install if prerequisite is not met

Hi James,

You are on the right track here. NOT IS_INSTALLED is the correct condition. It conditions the action to run only if IS_INSTALLED is empty (the search failed to find anything). So, it should have worked.

Just for your information, if you wanted to launch your action when the search succeeded, you would have simply used IS_INSTALLED as the condition.

Now, I am not sure what exactly you are conditioning. Are you conditioning the Launch File or Open URL custom action? If so, did you use it as an InstallExecuteSequence custom action or as a UI custom action? If used as a UI custom action, did you create the DoAction control event on the Finish button?

If this did not help much, do send me the .aip project file to support at advancedinstaller dot com so I can further investigate. Also include a link to this thread in your email.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
dotnetdude
Posts: 4
Joined: Wed Oct 08, 2008 6:47 am

Re: OPen Web Page AFTER install if prerequisite is not met

Hi,

All working perfectly (tested with both scenarios). I think we had some rubbish in there while testing which, when removed, all the new stuff worked fine.

Great product followed by great support!

Many thanks.

James.

Return to “Common Problems”