Posted 22 December 2005 - 16:04
The problem is, these product versions use many of the same files, some of which will have different versions some won't, across two different product versions. The docs seem to indicate that identical files/resources cannot be in different components across companies, not just products.
Must I use a common directory, like System32, for all shared components? What if the version of one of these shared components changes for a given version? Particularly for the activex controls, some of which will have version changes for the same upgrade path -- can I not have the same version of a resource installed for two different products in two separate folders in two different components/GUIDs? Will the identical COM registration entries for the same version of ActiveX in two directories cause conflicts between the two products?
Posted 22 December 2005 - 17:23
Posted 22 December 2005 - 19:32
I'm still wondering, though, whether registration for identical COM controls violate the "same path" criterion? Won't two identical COM controls generate numerous identical registry resources, even if the controls themselves are on different paths?
Posted 23 December 2005 - 08:40
As to COM servers: COM servers are registered per machine for a per machine install. This means there can be only once registration for any COM server that references the same registry keys. This means that your COM component will be initiated from the last location it was installed. IT is possible to work around this by using the isolation feature of Windows Installer. U can look this up in the SDK.
Posted 06 July 2006 - 00:15
MSI Factory Provider for ADO.NET 2.0 (Work In Progress)
99 Bottles Of Beer - Windows Installer
PM for personal communication only. Please ask questions in the forums.