Unregister at uninstall, or not?
I have repackaged an app that requires an OCX (TX4OLE.OCX) to be registered via Custom action. This works ok, I can also unregister it at uninstall. My question is, should I unregister at uninstall? Presumably unregistering will cause any other application which uses this file to fail. Is there any harm in leaving a file registered, after the file has been removed?
thanks
Mike
thanks
Mike
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
Jim101
19 years ago
where is the .ocx located??
If it is in it's own directory with the other application such as C:\Program Files\My App then I would unregsiter and ensure it is removed with the unintsall.
However if this is a shared OCX that sits in the c:\program files\common apps or c:\windows\ then I would leave it registered and installed, to ensure that tehre is no impact to any other apps.
hope this helps.
If it is in it's own directory with the other application such as C:\Program Files\My App then I would unregsiter and ensure it is removed with the unintsall.
However if this is a shared OCX that sits in the c:\program files\common apps or c:\windows\ then I would leave it registered and installed, to ensure that tehre is no impact to any other apps.
hope this helps.
Posted by:
WiseUser
19 years ago
Why are you using a custom action rather than the tables provided by MSI (class, appid, progid, etc), or at least the selfreg table (not recommended)?
Whether the component is removed or not will be automatic, assuming you follow the MSI standards (same component code across all versions of the ocx component, increment shared dll count for shared files, etc).
Whether the component is removed or not will be automatic, assuming you follow the MSI standards (same component code across all versions of the ocx component, increment shared dll count for shared files, etc).
Posted by:
MSIMaker
19 years ago
If you unregister it and another app needs it then as long as its in a component by itself with a keypath then the broken app should repair it regardless.
Posted by:
meastaugh1
19 years ago
Apologies for the delayed reply.
I had captured it using Wininstall LE and it added it to the selfreg table, but that only worked intermittently (I guess that's why it's not recommended).
I'm using Wininstall/MaSaI to edit. If I remove the component entries from Selfreg and leave the entries in Class, Appid, ProgID, will the installer use auto incrementing to detect when to unregister (ie when the count=0??).
Sorry, am a bit lost.
I had captured it using Wininstall LE and it added it to the selfreg table, but that only worked intermittently (I guess that's why it's not recommended).
I'm using Wininstall/MaSaI to edit. If I remove the component entries from Selfreg and leave the entries in Class, Appid, ProgID, will the installer use auto incrementing to detect when to unregister (ie when the count=0??).
Sorry, am a bit lost.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.