5 replies to this topic

[JoeThompson]

During installation, I create many registry entries.  I do so through the IDE (ISDev 7.02).  When my product is uninstalled, the registry entries are removed.  The problem is, we have a second product that uses the exact same registry key as I do.  This is probably a bad design decision on the part of the developers but I am stuck with the problem.  How do I prevent only certain keys from being removed at the "RemoveRegistryValues" action in the sequence.  Any suggestions?

Thank you,
Joe

[Ian Blake]

Make a component.  Place the registry key in it.  Use registry key as "keyfile" and use same component (with identical guid) in both products.

[JoeThompson]

Hi Ian,

I'm not quite sure I follow you...  When you said "Use registry key as "keyfile"" do you mean to right click it (in the IDE) and select "Set Key Path"?  Also, one important fact I left out is that I am not writing the other installation.  A coworker did and use IS 6.?.  I don't know if they have the same capability or not.

Thank you,
Joe

[Ian Blake]

Yes "key path" is a better way of saying it.

IS6 is not as clever as MSI.  One of MSI design goals with its universal component structure was to solve this type of problem.

You have a difficult probelm if you have one IS6 and one MSI installation.   The IS6 setup is completely ignorant.  The MSI is slightly better because with care in your design it will auto repair if the registry key is deleted by the uninstallation of the IS6 version.

[Stefan Krueger]

Moving to InstallShield 6 forum

[Taco Bell]

I know nothing about IS7, but for IS6 another way would be to create the registry entries in the script and disable logging around those entries.  That way they are not included in the uninstall routines.