/build/static/layout/Breadcrumb_cap_w.png

Best Practice for reverting registry during uninstall

Hi, what would be the Best Practice for the following situation?

One feature update existing registry keys. During uninstall, if i leave it as is, those reg keys get deleted. I already know the orginal values of those keys and I would like to revert back to those values during uninstall. There is probably many ways to do this but am looking for the Best Practice in this situation.

I already try isolating those reg keys in a feature, which i put a condition but i was unsuccessful, see here: http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning5718

Thanks for your input,

Bob

0 Comments   [ + ] Show comments

Answers (4)

Posted by: MSIPackager 15 years ago
3rd Degree Black Belt
0
Personally I'd use a wise/vbscript custom action conditioned with REMOVE="ALL"

Cheers,
Rob.
Posted by: unreal2me 15 years ago
Orange Senior Belt
0
Probably the easiest way, that is how I did it. But am still wondering if there is another way using conditions on components or else.

If anybody has other way to do it, feel free to suggest.

Thanks
Posted by: anonymous_9363 15 years ago
Red Belt
0
The WI engine has no easy native means to read and then record registry data (or any other data, come to that!)

I highlight 'easy' because you could conceivably read the entry and populate a property value with it but it would pretty soon get unwieldy, IMV. A CA is the best option.
Posted by: unreal2me 15 years ago
Orange Senior Belt
0
Sold !
Thanks
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