Hi,

Quick question.
Is it allways prefered to leave .dll and .ocx files when uninstall a software?
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
No, you want to leave the machine in the same state you found it before you installed your software.

P
Answered 07/18/2008 by: Inabus
Second Degree Green Belt

Please log in to comment
0
If you are absolutely positive the file is not used by anyother program.

The components that install dll or ocx files are typically set to shared - which is done by setting the 8 bit in the component attribute. During installation, a shared component will increment its file's reference counter by 1, and during removal it will substract by 1- whichever installer sets the counter to 0 removes the file.

Reference counter location:
HKLM\Software\Microsoft\Windows\CurrentVersion\Shareddlls

If you just delete the dll and ocx you risk the chance of orphaning their respective registration in the registry, which may not matter - it's just not clean.

Not sure if I answered your question directly - hope it helps...

-Grant
Answered 07/18/2008 by: gmorgan618
Blue Belt

Please log in to comment
0
ORIGINAL: gmorgan618
The components that install dll or ocx files are typically set to shared - which is done by setting the 8 bit in the component attribute. During installation, a shared component will increment its file's reference counter by 1, and during removal it will substract by 1- whichever installer sets the counter to 0 removes the file.

Reference counter location:
HKLM\Software\Microsoft\Windows\CurrentVersion\Shareddlls
Spot on, G.

aXz, please don't take the reference to the registry entry above as an invitation to mess with that entry: DON'T! As Grant says, if the component attribute is set, the Windows Installer engine will take care of whether or not the file can be removed.
Answered 07/18/2008 by: VBScab
Red Belt

Please log in to comment
0
Ok.... So what I could do is to check my package in the Software Manager repository and write down the .dll's and .ocx's that is in used in other application we use and dont uninstall them? So I dont uninstall files that other softwares using...
Answered 07/18/2008 by: aXz
Blue Belt

Please log in to comment
0
I assume these are MSI based packages we are talking about here (?)

If you have access to a Conflict Manager tool (and you mention that you have a Software Manager repository, so it sounds like you have) then this should be able to show you conflicting applications competing for the same resource (DLL,OCX &c)

In that case, there's no need to "write them down". The conflict management tools from the major players such as WISE or InstallShield have the option to automatically resolve the conflicts by synchronising the GUIDS of conflicting components - or you can do it manually if you have the time and/or interest.

Regards,

Spartacus
Answered 07/18/2008 by: spartacus
Black Belt

Please log in to comment
0
Thanks.... I will do that.
Answered 07/18/2008 by: aXz
Blue Belt

Please log in to comment
0
have a read of these they are all related to your current issues and many of your recent posts.

Reference counting
http://johnmcfadyen.spaces.live.com/blog/cns!9DD01136FC094724!136.entry

Packagers guide to windows registry
http://johnmcfadyen.spaces.live.com/blog/cns!9DD01136FC094724!151.entry

Wise Software manager in depthhttp://johnmcfadyen.spaces.live.com/blog/cns!9DD01136FC094724!189.entry
Answered 07/21/2008 by: jmcfadyen
Fifth Degree Black Belt

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