No, you can't.  Only a transform can be applied at the right time to change 
those values.

Furthermore, I would not recommend using Script for CustomActions ever.

-----Original Message-----
From: Dmitry Briliuk [mailto:[EMAIL PROTECTED]
Sent: Monday, September 25, 2006 12:29 PM
To: Rob Mensching
Cc: 'Mike Dimmick'; wix-users@lists.sourceforge.net
Subject: Re[2]: [WiX-users] install multiple instances of app?

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
RM> 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,
RM> so you 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
RM> to
RM> 16 to choose which components are installed for an instance. It then
RM> has a DLL custom action (type 1) to set the appropriate
RM> InstanceComponentSet.n property, which selects the required files.
RM> They must also be doing something else to associate the right files
RM> to the components, because Orca only shows the files once in the
RM> File table. Is it possible to edit the running copy of the MSI from a 
custom action?

RM> There are 17 MSIs supplied which appear to contain the same
RM> information, but have different package and product codes. I'm not
RM> quite sure what the purpose of the supplied patches in Release A is
RM> - it seems to merely change the product name from 'Microsoft SQL
RM> Server Desktop Engine' to 'SQL Server 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
RM> suppose 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
RM> a non-starter unless you're the SQL Server team.

RM> If you do want to make duplicate files from a single installer, you
RM> can use the <CopyFile> element under the <File> element to be duplicated.
RM> Presumably you could use some <Condition> to turn a particular
RM> <CopyFile> element on or off, but you'll have to author one
RM> <CopyFile> action for each instance you want to support. I don't
RM> think you'll be able to support having different versions in
RM> different directories, though - when you update, all 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
RM> 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
RM> server (i.e. into different web sites), or make multiple copies
RM> during single install.

RM> Each copy should have its own location (at least own Web.Config
RM> file) and perhaps own item in unistall list, preferable each copy to
RM> have own suffix, 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
RM> to make few packages with different guids, or ajust package/product
RM> guid at runtime, 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

Reply via email to