This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Registering a dll which need MFC9 - Order problem
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 07, 2008
06:08 AM
Registering a dll which need MFC9 - Order problem
Hi!
I need to register a dll which is compiled (not statically) with MFC 9.0
In the same installer I include the merge modules for MFC9
The problem is that the dll can not be register because MFC90 are not installed yet, if a run the installer twice all is ok because the MFC are installed.
Can I set the order of the installation for a Merge Module ??
Thanks in advance
I need to register a dll which is compiled (not statically) with MFC 9.0
In the same installer I include the merge modules for MFC9
The problem is that the dll can not be register because MFC90 are not installed yet, if a run the installer twice all is ok because the MFC are installed.
Can I set the order of the installation for a Merge Module ??
Thanks in advance
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 07, 2008
08:14 AM
Once a merge module is merged in, it is no longer a separate entity. It bcomes just some componenents in the MSI. So, no, there is no reliable way to order the merge module components.
You might look into installing the MFC files as a pre-requisite instead of through the merge modules. That is the only effective way I've found to workaround the way Microsoft installs files into the WinSxS directory.
You might look into installing the MFC files as a pre-requisite instead of through the merge modules. That is the only effective way I've found to workaround the way Microsoft installs files into the WinSxS directory.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 07, 2008
11:05 AM
We had a similar issue with dll registration. The workaround I used was to create two custom actions that called regsvr32 on the dll to manually register/unregister it.
The registration occurs as the very last step of the install and the unregistration occurs after UnregisterMIMEInfo (last step before any files are removed).
The registration occurs as the very last step of the install and the unregistration occurs after UnregisterMIMEInfo (last step before any files are removed).
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)