Hi
I am adding some registry values into a SubKey during an install but want to add / update them if they dont exist. If they do exist, i need to not update the values.
Thanks
Please have a look on our How do I prevent a file or registry entry from being uninstalled or repaired? article.I have followed your guide above however, the registry values are still getting reset when i do an update.
Regarding this, I've replied with more details on the other thread you opened. The solution to this is to use a patch. Please check my reply on the other thread.Update - add only the files that have changed, add only new registry keys - Size = 7mb
Then, in this case you can condition the installation of the specific component using the Condition field. You can add the OLDPRODUCTS condition or your custom condition for the values you want to preserve.The method you have shared shows the action on the key but not on the keys values. In the key, i have 12 values, 4 of which do not require a value change on an upgrade but the others might.
If the value already exists (even if is not created by a previous installation) it will not be overwritten. You can test this by manually creating a specific registry key using regedit and then set the "Never Overwrite" option for it in your project.This claims that a registry value would remain but as i correct in thinking that the in order for this work, the registry keys would need to have been created with the installer so that settings could be applied? In other words, if they existed before the install, they would be excluded from the said property settings?
Regarding this, next time please reply in the specific forum thread and avoid to mention the same issue in multiple threads (it's really hard for us to follow them across multiple threads). Thank you for understanding.Regarding my other post, I looked at patches but there are 2 issues have with them-
1. it would be an additional install phase id need to manage and we only want 1 file floating
2. they dont compile as .exe
i am not permitted by our IT to run patches. they have specific rules in place to prevent the download of msi files and patches (as far as they are concerned) can be as good as virus files which they cannot separate automatically so the easiest thing to do is blanket denial of msi files.