Attached Custom Action Behavior - 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!

tgillitzer
Posts: 36
Joined: Tue Dec 13, 2011 12:12 am

Attached Custom Action Behavior

So initially I didn't understand the behavior of an Attached Custom Action. It looked to me like you specify a path to a file and then, assuming that file is there on the machine installed, it would call it. However, now that I read the help file closer and look at the MSI file, it looks like it takes a copy of the file specified and sticks it in the MSI. This isn't what I want.

I want to be able to execute a file (exe, dll, etc) that I expect to be already on the system that I am installing on.

What is the best way to do this?

Thanks
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Attached Custom Action Behavior

Hello,

Usually, a custom action resource resides either on the development machine( package is built ) or in the install package it self. These case are covered by "Attached Custom Actions" and "Installed Custom Actions". For any other cases you should implement you own custom behavior.

For example, using "Launch File or Open URL" predefined custom action you can launch any resource already on target machine.
Here are a couple of articles that demonstrate its functionality:
http://www.advancedinstaller.com/user-g ... -file.html
http://www.advancedinstaller.com/user-g ... ation.html

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”