Hi,
If I have several product installations that share components, must these components have the same component code in all product installations and be set to shared or will it work with different component codes?
regards Fredrik
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.
Same component with different component key
Started by
fredrik.strom
, Mar 27 2006 14:51
2 replies to this topic
Posted 28 March 2006 - 10:36
If these components install to the same location (directory + file name is the same) then the same component GUID should be used even in different projects. The overall idea is that there is a 1:1 match between GUIDs and an absolute path. If the GUID changes so should the absolute path (a file rename would change the absolute path), and vice versa a change in the installation path should be accompanied by a changed GUID. One and only one GUID for every absolute path, and only one absolute path for each GUID.
Normally shared components are to be installed using merge modules - that is MSI modules with files and registry settings that can be merged into several other MSI packages. Component referencing should still work, however, if you keep the component GUIDs the same for the corresponding files between projects.
Normally shared components are to be installed using merge modules - that is MSI modules with files and registry settings that can be merged into several other MSI packages. Component referencing should still work, however, if you keep the component GUIDs the same for the corresponding files between projects.
Regards
-Stein Åsmul
-Stein Åsmul