Ron.Stordahl
6th May 2006 23:15 UTC

InstallLib functionality
I am using the following to install VB40032.dll in the appropriate system folder (OS dependent):

!insertmacro InstallLib DLL $Already_Installed REBOOT_PROTECTED "..\BPQ32_StagingArea\VB40032.DLL" $SYSDIR\VB40032.DLL $INSTDIR

My version of VB40032.dll I wish to install is the last one released by MS dated 1/12/1996 v4.0.29.24 freely available on their website.

Perhaps I shouldn't be worried about replacing an earlier version that might exist, perhaps installed by another application, after all this version is already over 10 years old. And they are supposed to be forward (or is that backward) compatible.

However can anyone tell me if the code above would do so, and if it does what changes would be needed so that it would just leave an earlier installed version alone?

Ron

kichik
7th May 2006 10:14 UTC

The last parameter should be $SYSDIR, not $INSTDIR. But in both ways, it will always replace older versions. If you don't want to replace, use SetOverwrite off and File instead of the Library macros.