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
FOLLOW US
Get the latest news in Application Packaging