Using Merge modules, and repackaging Merge modules
Hello,
An application I have to package uses the GDI+ library.
I had a look at the Installshield Website in order to download the last GDI+ Merge Module but, as you can see here http://www.installshield.com/downloads/modules.asp?prod=cx&lan=english&xmlUse=y the Microsoft GDI+ Library version is 5.1.3102.1355 whereas I have the 5.1.3102.1360 on my computer (And I don't know if it is the last revision).
So I would like to repackage the GDI+ Merge module in order to build one with the last version.
However, before doing that, I'm wondering if this could do something wrong. Does anybody "can" repackage Merge module ? Is there any restriction ?
i think that if I don't modify components and Merge module GUID, this shouldn't do something wrong, but... :-)
An application I have to package uses the GDI+ library.
I had a look at the Installshield Website in order to download the last GDI+ Merge Module but, as you can see here http://www.installshield.com/downloads/modules.asp?prod=cx&lan=english&xmlUse=y the Microsoft GDI+ Library version is 5.1.3102.1355 whereas I have the 5.1.3102.1360 on my computer (And I don't know if it is the last revision).
So I would like to repackage the GDI+ Merge module in order to build one with the last version.
However, before doing that, I'm wondering if this could do something wrong. Does anybody "can" repackage Merge module ? Is there any restriction ?
i think that if I don't modify components and Merge module GUID, this shouldn't do something wrong, but... :-)
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
WiseUser
19 years ago
Posted by:
babric
19 years ago
Yes, I did some google search before asking and found this webpage (and some others).
But, independently of gdi+, I would like you to answer my question :-)
I'm using XP pro but deploy for 2K too.
I know that the gdiplus.MSM is conditionned with VersionNT<501, so it would be only useful for win2K. Moreover, this .msm installs the .dll to TARGETDIR instead of SystemFolder, which is not very "smart" on behalf the .msm packager...
So I would like to operate some modifications...
But, independently of gdi+, I would like you to answer my question :-)
I'm using XP pro but deploy for 2K too.
I know that the gdiplus.MSM is conditionned with VersionNT<501, so it would be only useful for win2K. Moreover, this .msm installs the .dll to TARGETDIR instead of SystemFolder, which is not very "smart" on behalf the .msm packager...
So I would like to operate some modifications...
Posted by:
viv_bhatt1
19 years ago
IMHO if the merge module is vendor supplied still , you can change the destination / component condition of merge module to your requirement .
I see a problem only when you change the content of the merge module .
Again the information provided above is not published anywhere hence I am open to other opinions.
Cheers ,
V
I see a problem only when you change the content of the merge module .
Again the information provided above is not published anywhere hence I am open to other opinions.
Cheers ,
V
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.