VC80 merge modules and dependant custom actions on Vista - 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!

BobM
Posts: 11
Joined: Tue Aug 22, 2006 9:05 am

VC80 merge modules and dependant custom actions on Vista

Hi,

Installing on a clean Vista machine...

My application installer includes the VS2005 VC80 merge modules.

The installer runs some custom actions to perform registrations etc. The exe's that perform the custom actions depend on side-by-side installation of the VC80 files.

My problem is that when I call the custom actions, it appears that the VC80 side-by-side installation from the merge modules is not complete and I get side-by-side execution errors.

I found that only by moving the custom action right back to the InstallFinalize action, my custom action executes without a side-by-side error, but of course I cannot use Action Text at this point.

So, my question is, when I have an exe that depends on the VC80 side-by-side merge module being fully installed before I use the exe to perform a custom action, what is the proper way to sequence the custom action, or is there another way to do this?

I did try creating a seperate "pre-requisite" install project that includes the VC80 merge modules, and seting this as a pre-requisite in my main installer, but I think this is rather messy.

T.I.A.
Bob M
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi Bob,

A "Merge Module" is merged at build time. All the files are installed when the "InstallFiles" standard action reaches, so you need to schedule the custom action after this standard action. My suggestion is to schedule it under "InstallExecuteSequence->Install" section. "Action Text" can be set only for "Deferred" custom actions.

Also if the custom action needs to run in the system context set "Deferred with no impersonation" as "Execution Options".

Regards,
Gigi
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com/

Return to “Common Problems”