/build/static/layout/Breadcrumb_cap_w.png

How to deal DLL conflict in System32 folder?

Hello All.

I would like to ask on how to deal DLL with different versions as they called DLL hell.

An example of this is, I have 2 applications that use dll with SAME NAME and SAME LOCATION to drop but DIFFERENT VERSION.

What to do if these two applications will install together in one machine (OS-Windows 7) and also what if the other one was removed what will happen to the dll file?

Package A - file.dll version 1.0 to drop in System32 folder

Package B - file.dll version 2.0 to drop in System32 folder

 


0 Comments   [ + ] Show comments

Answers (2)

Posted by: jagadeish 10 years ago
Red Belt
1

Component Isolation should help you in this situation

Application isolation is one solution to component versioning conflicts, or DLL hell.

Isolation reduces versioning conflicts by modifying an application so it always loads the versions of components – such as DLLs – with which it was originally developed and tested


Comments:
  • How can apply component isolation using ISM or MST? I'm using installshield. Do you have procedure there? - ajcbasilio 10 years ago
Posted by: Badger 10 years ago
Red Belt
0

MSI file versioning will get the latest version to install. As long as the comp is shared (Att 8) then the dll ref count will increment.

So you will be able install either app in either order and remove them as and when you want to.

Make sure there is no Customaction registering the DLLs

 
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