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
- :
- MergeModule Dependency
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
‎Sep 18, 2008
08:18 AM
MergeModule Dependency
Hi,
I've a question to dependencies of 2 MergeModules.
Example:
MergeModule M1 in Version 1.0.0
MergeModule M2 in Version 1.0.0 depends on M1
Application A1 with M1 and M2
MergeModule M1 in new Version 1.1.0
Application A2 with M1 Version 1.1.0
Can I install Application A1 and after them A2?
Thanks
I've a question to dependencies of 2 MergeModules.
Example:
MergeModule M1 in Version 1.0.0
MergeModule M2 in Version 1.0.0 depends on M1
Application A1 with M1 and M2
MergeModule M1 in new Version 1.1.0
Application A2 with M1 Version 1.1.0
Can I install Application A1 and after them A2?
Thanks
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 18, 2008
11:09 AM
The merge module aspect of this question is largely unimportant; however there are two important questions:
Do the updated files in M1 1.1.0 cause any problems relative to the dependency of M2 1.0.0 on M1 1.0.0 - i.e. is the code side of the upgrade from M1 1.0.0 to M1 1.1.0 safe when other files are using it?
Are the installation components authored correctly such that the upgrade doesn't put the machine in a bad state - i.e. is M1 1.1.0 identical to M1 1.0.0, except with updated versions of its DLLs, at least if it's installing to a shared location? If it's installing side-by-side, or in an application-private location, this question may be less important.
If both questions are answered Yes - it's safe to update the files, and they will be updated correctly - then this should be fine. If the code is incompatible and they are installed to the same place, and/or if component rules are broken, this will likely cause a problem.
Do the updated files in M1 1.1.0 cause any problems relative to the dependency of M2 1.0.0 on M1 1.0.0 - i.e. is the code side of the upgrade from M1 1.0.0 to M1 1.1.0 safe when other files are using it?
Are the installation components authored correctly such that the upgrade doesn't put the machine in a bad state - i.e. is M1 1.1.0 identical to M1 1.0.0, except with updated versions of its DLLs, at least if it's installing to a shared location? If it's installing side-by-side, or in an application-private location, this question may be less important.
If both questions are answered Yes - it's safe to update the files, and they will be updated correctly - then this should be fine. If the code is incompatible and they are installed to the same place, and/or if component rules are broken, this will likely cause a problem.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 19, 2008
04:21 AM
Thanks for your answer, you've helped me.
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)