Hello !
I have install that contains one main feature and 3 subfeatures. We use third-part merge module, it includes a dll into our install. The problem is that we need the dll
into INSTALLDIR of each feature, actually we need up to 4 copies of the dll into different locations (if all features installed). Is there any way to achive this using merge module ? If no, can we do it by including the dll as component key file - for sure we do not want to include 4 copies of the same file into install.
Gena
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Put merge module content into two locations
Started by
Guennadi
, Nov 02 2004 14:58
1 reply to this topic
Posted 04 November 2004 - 17:00
Hello,
Why do you need three copies of the DLL? Is every copy different?
Assuming it's the same dll in every feature, just install the file once in a shared location where the application(s) will find it. You can help your application(s) find the Dll by placing it somewhere in the path (like "System32"), or you can use the "App Path" feature of windows to create a new path for your application. If it's a COM Dll the work is done for you by the registration.
Basically, you need to create a merge-module with a single component and a single file (in a single location). Copying the file to several folders would mean creating several components because the component code would have to be different. If this were a COM Dll (and using the same clsid), , you would also have to create isolated components.
Mandy.
Why do you need three copies of the DLL? Is every copy different?
Assuming it's the same dll in every feature, just install the file once in a shared location where the application(s) will find it. You can help your application(s) find the Dll by placing it somewhere in the path (like "System32"), or you can use the "App Path" feature of windows to create a new path for your application. If it's a COM Dll the work is done for you by the registration.
Basically, you need to create a merge-module with a single component and a single file (in a single location). Copying the file to several folders would mean creating several components because the component code would have to be different. If this were a COM Dll (and using the same clsid), , you would also have to create isolated components.
Mandy.