5 replies to this topic

[aakash.tiwari12@gmail.com]

Hi ,

 

After finishing the installation our installer should launch one exe.

It is launching properly but getting blocked by firewall of the system(windows 7,windows 8).

For launching i am using LaunchAppAndWait function.

 

 

Thanks,

Aakash

[Glytzhkof]

What is this EXE doing? Can it be embedded into the main application EXE?

[aakash.tiwari12@gmail.com]

Hi Glytzhkof

 

Actually this exe is FTPServer implementation. This should be launched when installation is finished regardless of starting main application.

[Glytzhkof]

I have no experience with Firewall exception setups, but I know the Wix toolkit provides a special extension to deal with this issue:

• http://wixtoolset.or...lexception.html
• http://www.joyofsetu...wall-extension/
• http://stackoverflow...xtension-in-wix

Other tools such as Installshield surely have features that can set up firewall exceptions, and you should also be able to write a custom action to do so: http://msdn.microsof...1(v=vs.85).aspx

[aakash.tiwari12@gmail.com]

Hi ,

 

Thank you  all for your help. i have solved this issue by creating a custom action with condition to execute only at installation time.

In this custom action i am running a VB script provided by microsoft to unblock the firewall for the my application.

 

Microsoft Link

http://msdn.microsof...1(v=vs.85).aspx

 

 

 

Thanks and Regards,

Aakash

Edited by aakash.tiwari12@gmail.com, 09 April 2014 - 13:39.

[Glytzhkof]

That's great. Have you also tested major upgrade scenarios? Another special case is patching. All these operations take place using the the same installation sequence (InstallExecuteSequence), and they will run all custom actions unless you condition them properly to not run.

 

I am rusty in these conditions, but it should be something like:

 

(NOT PATCH) AND (NOT UPGRADINGPRODUCTCODE) AND (NOT REMOVE=ALL) AND (NOT INSTALLED)

 

NOT PATCH = don't run during a patch operation

NOT UPGRADINGPRODUCTCODE = don't run during an uninstall triggered by a major upgrade

NOT REMOVE=ALL = don't run during a regular uninstall

NOT INSTALLED = don't run during a minor upgrade

 

I will need to check these conditions once I have time and access to my documents (don't have access to my script repository right now), but you can check them yourself by making a simulated upgrade. This is something you should always do when delivering a setup. You can also make the script itself smarter by realizing it has been run before (write to registry), or allow it to run and discover that the firewall settings are ok.

 

Edit: Just adding this link to a sheet with conditions  so you can verify the conditions on your own. It is too easy to make mistakes in those conditions, be careful.

Edited by Glytzhkof, 09 April 2014 - 14:49.