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

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Personally I'd use a wise/vbscript custom action conditioned with REMOVE="ALL"

Cheers,
Rob.
Answered 03/06/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
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
Answered 03/06/2009 by: unreal2me
Orange Senior Belt

Please log in to comment
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.
Answered 03/09/2009 by: VBScab
Red Belt

Please log in to comment
0
Sold !
Thanks
Answered 03/09/2009 by: unreal2me
Orange Senior Belt

Please log in to comment
Answer this question or Comment on this question for clarity