Hi Igor,
The problem is that if the custom action is placed under InstallFinalize it is set as "Immediate" so it will get executed before the chained packages. Can you please try to scheduled the custom action under "InstallIIS" standard action, as "Deferred with no impersonation" and try the package again?
To understand what is the difference between immediate and deferred custom actions I recommend the following article:
http://www.advancedinstaller.com/user-g ... tions.html
The above article will help you understand a lot of what is going one when the installer enters the execute stage and starts modifying the system, i.e. installing the new resources.
Back to your custom action, I am still no 100% sure it will work because of the way Windows Installer handles chained packages. What happens when you install a chained package is that Windows Installer merges the system changes into a single transaction, so the files/registry entries from the chained package will be placed on the machine at the same time with the ones from the main one. Theoretically this should allow the custom action to find the required resources when running as deferred.
Regards,
Bogdan
FOLLOW US
Get the latest news in Application Packaging