Hello Arthur,
If I add .Net Framework 2.0 as a launch condition, that won't actually install .Net Framework 2.0, will it? If it's not installed, then the user won't be able to run my installer.
Yes, this is true. The users will have to manually install .Net Framework 2.0 ( if isn't already installed) before running your installation package.
I think I can see another way around this - if I add a restart after installing .Net Framework 2.0, then the VB exe should work ok. That would mean two reboots before the install actually starts, and then I also need another one at the end...
I'm afraid this is a wrong approach. As I mentioned in my previous post, searches from prerequisites install conditions are performed before the prerequisites installation starts. So, your VB executable will be scheduled before .Net Framework 2.0 prerequisite installation will start.
However, if my previous solutions aren't suitable for your scenario, then you can try the following workaround:
- Create a separate installation package (i.e. ANTIVIRUS_PACKAGE) which will contain the antivirus program added as pre-install prerequisite using "Reboot system after installing this prerequisite" option. Here you can add your search done by the VB executable for antivirus prerequisite.
- Create your main installation package and add .Net Framework 2.0 and ANTIVIRUS_PACKAGE as pre-install prerequisite. Also, ANTIVIRUS_PACKAGE prerequisite should be set to always install.
All the best,
Daniel
FOLLOW US
Get the latest news in Application Packaging