Understanding RegKey Conflicts with Wise Studio.
Hi all,
I'm still a bit new to understanding some conflicts I see commonly in the "Conflict Manager" in Wise Studio.
Depending on the package, sometimes I see a lot of conflicts between other packages with RegKeys and most of them have a "Data Value" of "DEFALUT".
Could I just remove these keys from the Installation Expert to lighten the package and reduce the number of Conflicts it's reporting? For the most part I am sure it's not hurting anything if I leave it, but what would be a best practice and when should remove them.
For most of them, the Operation will be to "Create/Update key and value", but the Values are default. So why would the vendor MSI create these keys and what is the purpose of these "Default Value" keys being created?
Anyone?
I'm still a bit new to understanding some conflicts I see commonly in the "Conflict Manager" in Wise Studio.
Depending on the package, sometimes I see a lot of conflicts between other packages with RegKeys and most of them have a "Data Value" of "DEFALUT".
Could I just remove these keys from the Installation Expert to lighten the package and reduce the number of Conflicts it's reporting? For the most part I am sure it's not hurting anything if I leave it, but what would be a best practice and when should remove them.
For most of them, the Operation will be to "Create/Update key and value", but the Values are default. So why would the vendor MSI create these keys and what is the purpose of these "Default Value" keys being created?
Anyone?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Many applications use a registry key on its own, with no value or data, to store settings. For example, they may use a structure like HKLM\Software\VendorName\SuiteName\ApplicationName\VersionNumber. Removing them might reduce your package size by a couple of bytes but, in the process, render the application useless. Leave them.
Posted by:
jmcfadyen
13 years ago
on another note:
Wise also produces a number of false positives when referring to registry conflicts.
An example of something like this would show a conflict but not actually be a conflict
HKLM\Software\Packages\[ProductName]\Test = [ProductVersion]
this is a bad example but shows how easily Wise can make a mess of such references.
If you had the same key in two applications you would find the actual paths are completely different. Wise does not resolve these values during import and often results in conflicting info when in actual fact the resolved values would report something different.
Wise also produces a number of false positives when referring to registry conflicts.
An example of something like this would show a conflict but not actually be a conflict
HKLM\Software\Packages\[ProductName]\Test = [ProductVersion]
this is a bad example but shows how easily Wise can make a mess of such references.
If you had the same key in two applications you would find the actual paths are completely different. Wise does not resolve these values during import and often results in conflicting info when in actual fact the resolved values would report something different.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
