Comments on: How to Implement DLL Isolation in Wise Package Studio? http://www.msigeek.com/309/implementing-dll-isolation Microsoft Guides, Windows Blog and Tech Tips Tue, 07 Feb 2012 16:43:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Vijay Raj http://www.msigeek.com/309/implementing-dll-isolation/comment-page-1#comment-260 Vijay Raj Sun, 29 Mar 2009 15:36:00 +0000 http://174.36.239.128/~msigeek/implementing-dll-isolation/#comment-260 You can create isolated components so that a destination computer's existing files will not be overwritten with your application's installed files. If an existing file is overwritten with a file that you are installing, there may be problems with an application that existed on the computer before the install. <br/><br/>When a file has been included in an isolated component, the file will be installed into the application's installation directory rather than a Windows system directory.<br/><br/>In this case, one of the components can be placed in the same directory as the application, and a file created with the same name as the application executable, with an extension .LOCAL. Then the local component will be used by preference by this application (other applications will use the non-local component, or their own local components).<br/><br/>Because the same registry entries are used for both copies of the component, the components need to be binary compatible for this to work. Hence these registry components are given a shared count under properties. You can create isolated components so that a destination computer’s existing files will not be overwritten with your application’s installed files. If an existing file is overwritten with a file that you are installing, there may be problems with an application that existed on the computer before the install.

When a file has been included in an isolated component, the file will be installed into the application’s installation directory rather than a Windows system directory.

In this case, one of the components can be placed in the same directory as the application, and a file created with the same name as the application executable, with an extension .LOCAL. Then the local component will be used by preference by this application (other applications will use the non-local component, or their own local components).

Because the same registry entries are used for both copies of the component, the components need to be binary compatible for this to work. Hence these registry components are given a shared count under properties.

]]>