It's worse than that. Components should always have the same path, so you really need to generate new GUIDs for all the components for each instance.
MSDE 2000 duplicates every component that needs to be isolated to an instance and uses a condition 'InstanceComponentSet.n' where n is 1 to 16 to choose which components are installed for an instance. It then has a DLL custom action (type 1) to set the appropriate InstanceComponentSet.n property, which selects the required files. They must also be doing something else to associate the right files to the components, because Orca only shows the files once in the File table. Is it possible to edit the running copy of the MSI from a custom action? There are 17 MSIs supplied which appear to contain the same information, but have different package and product codes. I'm not quite sure what the purpose of the supplied patches in Release A is - it seems to merely change the product name from 'Microsoft SQL Server Desktop Engine' to 'SQL Server 2000 Desktop Edition'. The actual files are in a CAB shared by all the MSIs. This is what I'm able to guess by viewing the MSIs in Orca. I don't suppose anyone from the SQL Server team would like to explain how exactly it works? Given the extreme complexity, I'd say that trying to make independently-uninstallable and independently-updatable instances is a non-starter unless you're the SQL Server team. If you do want to make duplicate files from a single installer, you can use the <CopyFile> element under the <File> element to be duplicated. Presumably you could use some <Condition> to turn a particular <CopyFile> element on or off, but you'll have to author one <CopyFile> action for each instance you want to support. I don't think you'll be able to support having different versions in different directories, though - when you update, all folders would be updated at the same time. -- Mike Dimmick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dmitry Briliuk Sent: 21 September 2006 10:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] install multiple instances of app? It is required to intall web application multiple times on the same server (i.e. into different web sites), or make multiple copies during single install. Each copy should have its own location (at least own Web.Config file) and perhaps own item in unistall list, preferable each copy to have own suffix, i.e. "My application on Website1"/"My application on Website2", etc. How to do this? WiX msi allows only one instance. The only idea was to make few packages with different guids, or ajust package/product guid at runtime, but it seems not a good style. TIA ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE V _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
