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   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer



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

Answered 04/21/2014 by: jagadeish
Red Belt

  • How can apply component isolation using ISM or MST? I'm using installshield. Do you have procedure there?
  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
Please log in to comment
Answer this question or Comment on this question for clarity



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

Answered 04/22/2014 by: Badger
Red Belt

Please log in to comment