ICE ICE Baby
Ok, maybe not. :)
Is it mandatory that I fix ICE08 errors? (Duplicate GUIDS). I have 2 components with the same GUIDS. One of the components is conditionalized "Version9X OR (VersionNT < 500)".
It looks like it's ok unless it meets the condition.
Also, I have Keypaths being set to the SystemFolder. Why would a vendor do this?
Finally, there are some 3rd party files being installed into a shared directory without the shared dll ref count flag set. I would assume that if these files have never existed or if we plan to NEVER have these files installed with any other package, then we're ok, otherwise we will probably want to fix this?
As always, thanks for the assistance!
Is it mandatory that I fix ICE08 errors? (Duplicate GUIDS). I have 2 components with the same GUIDS. One of the components is conditionalized "Version9X OR (VersionNT < 500)".
It looks like it's ok unless it meets the condition.
Also, I have Keypaths being set to the SystemFolder. Why would a vendor do this?
Finally, there are some 3rd party files being installed into a shared directory without the shared dll ref count flag set. I would assume that if these files have never existed or if we plan to NEVER have these files installed with any other package, then we're ok, otherwise we will probably want to fix this?
As always, thanks for the assistance!
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
turbokitty
17 years ago
Is the content of each component identical? Is there a condition on the second component?
Keypath to system folder, I suppose that could be an issue if the file can't be delivered due to something already existing on the box with that name. I'm not sure that's a big deal.. I've seen lots of MSI's coded that way. Am I missing something? probably..
Things in shared folders should be marked as shared or permanent.. yes.
Keypath to system folder, I suppose that could be an issue if the file can't be delivered due to something already existing on the box with that name. I'm not sure that's a big deal.. I've seen lots of MSI's coded that way. Am I missing something? probably..
Things in shared folders should be marked as shared or permanent.. yes.
Posted by:
AngelD
17 years ago
I have 2 components with the same GUIDS
If this is a vendor MSI I wouldn't fix it, just make sure the condition for both of these components will not be true.
It it's not a vendor MSI then change have different GUID for the components.
Also, I have Keypaths being set to the SystemFolder. Why would a vendor do this?
This would be used if you only want to install the component's resources (such as files & registry) but do not want to trigger a repair for this component as the keypath (SystemFolder) would not be broken (missing).
I would assume that if these files have never existed or if we plan to NEVER have these files installed with any other package, then we're ok, otherwise we will probably want to fix this?
I agree with turbokitty, if your are unsure if they will pre-exist or no other package will install these files you should add the ref count for these components.
If this is a vendor MSI I wouldn't fix it, just make sure the condition for both of these components will not be true.
It it's not a vendor MSI then change have different GUID for the components.
Also, I have Keypaths being set to the SystemFolder. Why would a vendor do this?
This would be used if you only want to install the component's resources (such as files & registry) but do not want to trigger a repair for this component as the keypath (SystemFolder) would not be broken (missing).
I would assume that if these files have never existed or if we plan to NEVER have these files installed with any other package, then we're ok, otherwise we will probably want to fix this?
I agree with turbokitty, if your are unsure if they will pre-exist or no other package will install these files you should add the ref count for these components.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
