My installation needs to check for a DLL before being installed, so I added the DLL to the prerequisites. The problem I have is that even if the DLL exists, advanced installer-created installation claims it does not exist. I have this problem with one particular DLL, it works well for other DLL's.
What I noticed that is different about this DLL is that it does not have a version info in its resources (no Version tab in Explorer properties also). So I guess that when advanced installer tries to extract version info it fails.
Any fix/workaround?
Thanks,
KIV
Suggested Articles
Hi,
When the "File Version" is used as search criteria for a prerequisite then the bootstrapper is looking for the version of that DLL to see if the prerequisite is already installed or not. If your DLL does not have version information then change the search criteria or search for other file.
But if your package needs only to check if that DLL is installed then you can use a "File Search" with a "Launch condition".
On how to create a file search and a launch condition please see:
http://www.advancedinstaller.com/user-guide/search.html
http://www.advancedinstaller.com/user-g ... tions.html
Also you can use the "Launch Condition" wizard because is more easy to use.
Please let me know if this is not what you want.
Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
When the "File Version" is used as search criteria for a prerequisite then the bootstrapper is looking for the version of that DLL to see if the prerequisite is already installed or not. If your DLL does not have version information then change the search criteria or search for other file.
But if your package needs only to check if that DLL is installed then you can use a "File Search" with a "Launch condition".
On how to create a file search and a launch condition please see:
http://www.advancedinstaller.com/user-guide/search.html
http://www.advancedinstaller.com/user-g ... tions.html
Also you can use the "Launch Condition" wizard because is more easy to use.
Please let me know if this is not what you want.
Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
Hi,
Thanks, I used the Launch condition wizard and it works fine for me know. Just one question - with the condition wizard that I get is a pop-up message with just text. I really would like to link to a URL from there, to get the user to the readme with instructions what to do.
Any suggestions how to do this (I assume with custom actions, but I could not get it to work). What I need is - if the search doesn't find the file to launch a browser on a URL and abort the install.
Thanks,
KIV
Thanks, I used the Launch condition wizard and it works fine for me know. Just one question - with the condition wizard that I get is a pop-up message with just text. I really would like to link to a URL from there, to get the user to the readme with instructions what to do.
Any suggestions how to do this (I assume with custom actions, but I could not get it to work). What I need is - if the search doesn't find the file to launch a browser on a URL and abort the install.
Thanks,
KIV
Hi,
Note that the launch condition is used only to check if a particular application is installed or not and if not an error message will be displayed.
If your package needs other application to be installed first then you need to use prerequisites. If the file used to determine if the prerequisite is installed or not does not have a version then leave the "Minimum" and "Maximum" fields empty (in this check AI will check for the existence of that file). For more details about how to use prerequisites please see:
http://www.advancedinstaller.com/user-g ... tware.html
If all you need is a launch condition then you can launch the browser with a URL if the file is not found like this:
Switch to "Custom Actions" page and select "InstallUISequence->AppSearch". Choose "Add Predefined Custom Action->Launch File or Open URL" from the context menu. As "Execution Condition" for the custom action use: (NOT RESULT_PROPERTY) AND (NOT Installed). Where RESULT_PROPERTY is the property of the search.
Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
Note that the launch condition is used only to check if a particular application is installed or not and if not an error message will be displayed.
If your package needs other application to be installed first then you need to use prerequisites. If the file used to determine if the prerequisite is installed or not does not have a version then leave the "Minimum" and "Maximum" fields empty (in this check AI will check for the existence of that file). For more details about how to use prerequisites please see:
http://www.advancedinstaller.com/user-g ... tware.html
If all you need is a launch condition then you can launch the browser with a URL if the file is not found like this:
Switch to "Custom Actions" page and select "InstallUISequence->AppSearch". Choose "Add Predefined Custom Action->Launch File or Open URL" from the context menu. As "Execution Condition" for the custom action use: (NOT RESULT_PROPERTY) AND (NOT Installed). Where RESULT_PROPERTY is the property of the search.
Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com