execution of custom action - 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!

Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: execution of custom action

Hi,

This happens because your custom action have no execution conditions, therefore are executed all the time, install/uninstall/repair.

To have a custom action run only during the install you need to set its execution condition to "NOT Installed".

To have a custom action run only during the uninstall you need to set its execution condition to "REMOVE="ALL"".

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: execution of custom action

Hi,

I am not sure why this is happening. It could be that all of them were launched but one of them failed silently. To see exactly which of them were launched
you can create a verbose log when installing and uninstalling the package.

Still, the execution conditions I mentioned should be used, as these are the ones that will decide if the custom action is executed during install/uninstall.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: execution of custom action

Hi,
I wonder if there is some issue when using Java project for .NET addin project
There is no problem. A Java project is the same as a Professional one, but also contains some Java features.
Also how to create one build for debug, one for release.
debug will use dlls from bin\debug,
release will use dlls from bin\release
Usually only one build is used:
- convert your project to use path variables for your source files
- when you want a release build change the variable to use "bin\release"
- when you want a debug build change the variable to use "bin\debug"

Path variables can also be set from command line so you can use automated scripts for builds.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: execution of custom action

Hi,

To convert the existing absolute paths to path variables use the Convert Paths wizard ( menu bar -> “Project” -> “Convert Paths...”).

You can edit the existing path variables from the menu bar -> “Options” -> “Path Variables...”.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: execution of custom action

Hi,
I add path variables but in File and folder, when I select source path, it is still point to physical disk folders.
Are you referring to source path field in Edit File dialog or the list column? Edit File dialog should display the path variable and the list column will always show the resolved value.

The general approach is this:
- remove all your files and folders from Files and Folders page
- define your custom path variable to use the current files path
- add your files and folders
- use Project -> Convert Paths wizard to convert the file paths
- when you want to change the source simply edit your custom path variable through Options -> Path Variables

Please note that your custom path variable will not be used for files which are already using predefined path variables. So you need to remove and add the files again to convert them.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”