Hello Rob, Thanks
Also, is it possible to change ProductCode, ProductName and PackageId from inside msi by calling script? So, the msi will detect existing product by comparing it with new guid, generated by script? I have tried something like this: Session.Property["ProductName"] = "new product name" Session.Property["ProductCode"] = new_guid but it does not affect on installed product properties, however in logs, after PublishProperties it shows values assigned by script. Friday, September 22, 2006, 8:25:28 AM, you wrote: RM> There is a topic in the MSI SDK about creating multiple instance MSI files. RM> It is pretty tricky and a fair bit of work (not much different than RM> proposed, but transforms are used to minimize the number of MSIs RM> distributed). RM> I do *not* recommend using CopyFile to try and solve this problem. RM> -----Original Message----- RM> From: [EMAIL PROTECTED] RM> [mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick RM> Sent: Thursday, September 21, 2006 03:43 RM> To: Dmitry Briliuk; wix-users@lists.sourceforge.net RM> Subject: Re: [WiX-users] install multiple instances of app? RM> It's worse than that. Components should always have the same path, so you RM> really need to generate new GUIDs for all the components for each instance. RM> MSDE 2000 duplicates every component that needs to be isolated to an RM> instance and uses a condition 'InstanceComponentSet.n' where n is 1 to RM> 16 to choose which components are installed for an instance. It then has a RM> DLL custom action (type 1) to set the appropriate InstanceComponentSet.n RM> property, which selects the required files. They must also be doing RM> something else to associate the right files to the components, because Orca RM> only shows the files once in the File table. Is it possible to edit the RM> running copy of the MSI from a custom action? RM> There are 17 MSIs supplied which appear to contain the same information, but RM> have different package and product codes. I'm not quite sure what the RM> purpose of the supplied patches in Release A is - it seems to merely change RM> the product name from 'Microsoft SQL Server Desktop Engine' to 'SQL Server RM> 2000 Desktop Edition'. The actual files are in a CAB shared by all the MSIs. RM> This is what I'm able to guess by viewing the MSIs in Orca. I don't suppose RM> anyone from the SQL Server team would like to explain how exactly it works? RM> Given the extreme complexity, I'd say that trying to make RM> independently-uninstallable and independently-updatable instances is a RM> non-starter unless you're the SQL Server team. RM> If you do want to make duplicate files from a single installer, you can use RM> the <CopyFile> element under the <File> element to be duplicated. RM> Presumably you could use some <Condition> to turn a particular <CopyFile> RM> element on or off, but you'll have to author one <CopyFile> action for each RM> instance you want to support. I don't think you'll be able to support having RM> different versions in different directories, though - when you update, all RM> folders would be updated at the same time. RM> -- RM> Mike Dimmick RM> -----Original Message----- RM> From: [EMAIL PROTECTED] RM> [mailto:[EMAIL PROTECTED] On Behalf Of Dmitry Briliuk RM> Sent: 21 September 2006 10:31 RM> To: wix-users@lists.sourceforge.net RM> Subject: [WiX-users] install multiple instances of app? RM> It is required to intall web application multiple times on the same server RM> (i.e. into different web sites), or make multiple copies during single RM> install. RM> Each copy should have its own location (at least own Web.Config file) and RM> perhaps own item in unistall list, preferable each copy to have own suffix, RM> i.e. "My application on Website1"/"My application on Website2", etc. RM> How to do this? WiX msi allows only one instance. The only idea was to make RM> few packages with different guids, or ajust package/product guid at runtime, RM> but it seems not a good style. -- Dmitry ------------------------------------------------------------------------- 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
