/build/static/layout/Breadcrumb_cap_w.png

Self-repair also repairing value of regkey?

Hi there,
I hope anyone can give me a hint...
In my MSI I've got two HKCU keys, which I both want to have the value "0". When I delete these keys and start the program again, the values are being created by self-repair. So it works, actually.
But: if the value of the keys changes (e.g. to "1"), self-repair doesn't correct it. But I always want it to be "0", when the program starts.

Any possibilty to handle that?

Please consider: I'm quite new to packaging (and sorry for my bad english...)

edit: Or just tell me that it's not possible at all...
Asked 13 years ago 1787 views
0 Comments   [ + ] Show comments

Answers (5)

Posted by: sridtech 13 years ago
Senior Yellow Belt
0
It's possible. One way to accomplish this would be to create a simple routine that checks the registry value and resets it to '0' prior to calling the actual program. You could then reassign any shortcuts to point to this wrapper routine.
Posted by: anonymous_9363 13 years ago
Red Belt
0
Wrong, I'm afraid. Repair/self-healing only replaces missing data, not mismatched data. If the file/registry value is present, it won't be repaired.
Posted by: Nicole 13 years ago
Senior Yellow Belt
0
I also thought about creating a CA, which checks on the value of the key. But that won't work.
OK, so I'll forget that...

Thanks for your help, both!
Posted by: anonymous_9363 13 years ago
Red Belt
0
Why not do something via a start-up or the login script?
Posted by: sridtech 13 years ago
Senior Yellow Belt
0
My suggestion was not to create a custom action in the MSI. I'm assuming the 2 registry entries contained in your MSI have a default value set to '0'. Now, if the program (EXE) that is part of your MSI is the one causing the value to change from '0' to '1', then you could create a wrapper routine (EXE) that checks the reg value and resets it to '0' prior to calling the application EXE. Take this wrapper routine (EXE), make it part of your MSI install (you could drop it in the application directory), realign any shortcuts that point to the application EXE in the MSI to now point to this wrapper EXE. After the updated MSI is installed, each time you launch your program via the shortcut or double-clicking the wrapper EXE, the registry check would be enforced. I must add this is not the most elegant solution, but should get the job done.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ