Howto get shared components to laod from MSM - I just don't get it!
So, I just don't get it.
I have a vendor MSI with a load of custom actions installing items like "Global_VC_CRT.51D569E0_8A28_11D2_B962_006097C4DE24" (msvcrt.dll) and I want to banish those and instead get it to use a standard MSM.
What do I do - delete the "Global_VC_CRT.51D569E0_8A28_11D2_B962_006097C4DE24" component (and the others like it) and check-off(on actually) the appropriate redistributable item? (I'm using IS 10.5 / AS 6.0) Or do I leave the component active as it is, and simply delete the file out of the cab (with the redist checked)?
Is there an easy way to do this?
Supplementary question:
In the MSI Resdist window, there are a bunch of items like -- "MSDAO.02D9DBC1_9A48_4505_8F4B_5ECCEF8DABA4" which points nowhere, but which seems to concern in this example dao350.dll - which should be in a Microsoft MSM. So why is it here, and how can I get the MSI to use the MSM and not what it has in its files.cab? Just delete the file out of the cab and pray?
Everybody talks about using MSM's for shared components, but the vendors can't be bothered to do it, it would seem, (or maybe they do, but if they don't separate it out and let me use the same MSM for everybody, it doesn't do me much good). IS documentation is really lame when you are trying to figure out how to fix something from a vendor as opposed to creating your own from scratch.
Thanks for any help or for pointers to worthwhile documentation on how to cope with shared components.
William
I have a vendor MSI with a load of custom actions installing items like "Global_VC_CRT.51D569E0_8A28_11D2_B962_006097C4DE24" (msvcrt.dll) and I want to banish those and instead get it to use a standard MSM.
What do I do - delete the "Global_VC_CRT.51D569E0_8A28_11D2_B962_006097C4DE24" component (and the others like it) and check-off(on actually) the appropriate redistributable item? (I'm using IS 10.5 / AS 6.0) Or do I leave the component active as it is, and simply delete the file out of the cab (with the redist checked)?
Is there an easy way to do this?
Supplementary question:
In the MSI Resdist window, there are a bunch of items like -- "MSDAO.02D9DBC1_9A48_4505_8F4B_5ECCEF8DABA4" which points nowhere, but which seems to concern in this example dao350.dll - which should be in a Microsoft MSM. So why is it here, and how can I get the MSI to use the MSM and not what it has in its files.cab? Just delete the file out of the cab and pray?
Everybody talks about using MSM's for shared components, but the vendors can't be bothered to do it, it would seem, (or maybe they do, but if they don't separate it out and let me use the same MSM for everybody, it doesn't do me much good). IS documentation is really lame when you are trying to figure out how to fix something from a vendor as opposed to creating your own from scratch.
Thanks for any help or for pointers to worthwhile documentation on how to cope with shared components.
William
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
williamp
18 years ago
Maybe I'm starting to get it now .... somebody tell me if I'm right?
-- the component "Global_VC_CRT.51D569E0_8A28_11D2_B962_006097C4DE24" has such a long name because it DOES come from an MSM and Install Shield verifies that it is the same version as the MSM in its local repository. All I have to do is document it, then ignore it.
Is that true?
-- the object in the redist window "MSDAO.02D9DBC1_9A48_4505_8F4B_5ECCEF8DABA4" which points nowhere, also comes from MSM, but NOT the SAME version as the one in Install Shield's local repository (or maybe I don't even have the wrong version), so this is IS's way of flagging it.
Is that true? If so, what are my options?
Thanks for any comments.
-- the component "Global_VC_CRT.51D569E0_8A28_11D2_B962_006097C4DE24" has such a long name because it DOES come from an MSM and Install Shield verifies that it is the same version as the MSM in its local repository. All I have to do is document it, then ignore it.
Is that true?
-- the object in the redist window "MSDAO.02D9DBC1_9A48_4505_8F4B_5ECCEF8DABA4" which points nowhere, also comes from MSM, but NOT the SAME version as the one in Install Shield's local repository (or maybe I don't even have the wrong version), so this is IS's way of flagging it.
Is that true? If so, what are my options?
Thanks for any comments.
Posted by:
TomB
18 years ago
Williamp,
Those components are from MS MSM files. We use them all the time at my office for share dlls. If it is in a Vendor MSI I would not remove it, but be assurned that is the standards naming convention I have seen for the MS MSM files.
If you are using IS then you should have a Redist option that should show the MergeModules selected in the package.
Those components are from MS MSM files. We use them all the time at my office for share dlls. If it is in a Vendor MSI I would not remove it, but be assurned that is the standards naming convention I have seen for the MS MSM files.
If you are using IS then you should have a Redist option that should show the MergeModules selected in the package.
Posted by:
williamp
18 years ago
Hi Tom, thanks for your comments.
So, the 3 or 4 items such as "MSDAO.02D9DBC1_9A48_4505_8F4B_5ECCEF8DABA4" which are in fact in the Redist window seem to me to have been from somebody's MSM (the vendor's), but are of a version not in mine. So how can I, preferably by using a transform, yank that item, and use one from my DAO MSM instead? And, is this something I should be doing?
Thanks for comments!
William
So, the 3 or 4 items such as "MSDAO.02D9DBC1_9A48_4505_8F4B_5ECCEF8DABA4" which are in fact in the Redist window seem to me to have been from somebody's MSM (the vendor's), but are of a version not in mine. So how can I, preferably by using a transform, yank that item, and use one from my DAO MSM instead? And, is this something I should be doing?
Thanks for comments!
William
ORIGINAL: TomB
Williamp,
Those components are from MS MSM files. We use them all the time at my office for share dlls. If it is in a Vendor MSI I would not remove it, but be assurned that is the standards naming convention I have seen for the MS MSM files.
If you are using IS then you should have a Redist option that should show the MergeModules selected in the package.
Posted by:
TomB
18 years ago
williamp,
Before you remove and replace the MSM you should make sure that your versions of the files work with that particular application.
I would suggest you leave the vendor MSM as is, but depending on your company policy i guess you might not be able to do that.
If you are in InstallShild and you open the MSI then go to the Redistributabl section, do you see the MSM and can you just uncheck it?
If not then you may have to manually remove it. That would meen you would have to remove all the associated items from the components table, featurecompnents table, all class entires, typelib, and progID,custom actions, any actions in any of the sequence tables, modulecomponents, moduledependency,modulesignature, if exists.
It might just be eaiser to find the MSM the manufacture used and download it and add it to your MSM Cache and you might be able to simply uncheck it in the Install Shield Console.
Before you remove and replace the MSM you should make sure that your versions of the files work with that particular application.
I would suggest you leave the vendor MSM as is, but depending on your company policy i guess you might not be able to do that.
If you are in InstallShild and you open the MSI then go to the Redistributabl section, do you see the MSM and can you just uncheck it?
If not then you may have to manually remove it. That would meen you would have to remove all the associated items from the components table, featurecompnents table, all class entires, typelib, and progID,custom actions, any actions in any of the sequence tables, modulecomponents, moduledependency,modulesignature, if exists.
It might just be eaiser to find the MSM the manufacture used and download it and add it to your MSM Cache and you might be able to simply uncheck it in the Install Shield Console.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.