[WiX-users] Burn / MsiProperty / Repair mode
Hello,
I have a bundle with a slightly customized UI ( see
http://stackoverflow.com/questions/12323106/customising-the-wix-burn-theme-with-additional-inputs
) to display an Editbox, and passing the value as a MsiProperty to an
underlying MsiFile.
In the Theme file :
...
And in the bundle.wxs file :
Just in case it matters, this property is used to customize the target of a
shortcut created by the MSI installer.
I'd like to know if it's possible to have the same behavior in Repair mode,
i.e. user executes the bundle, type another value in the EditBox, and the
shortcut is updated. I've tested the behavior with 'msiexec /fvs
package.msi XXX=NewValue' and the shortcut is correctly updated.
So I've modified the 'Modify' page in the bundle's theme file to include
the EditBox, but when I execute through the bundle, the variable is not
passed to the MsiPackage. Log file just say :
[23C4:2C04][2014-10-17T12:26:46]i301: Applying execute package:
Foo.Bar.msi, action: Repair, path: C:\ProgramData\Package
Cache\{EE22E609-7D8B-4CEF-BB54-A6ADD164E181}v1.0.2\Foo.Bar.msi, arguments:
' MSIFASTINSTALL="7" XXX="" YYY="" ZZZ=""
Is there anything I'm missing here ?
Best regards,
--
Gilles QUERRET
Riverside Software
15d route de Bellevue • 69440 Mornant • France
Mob : +33 662.525.532
--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn and variables
Thanks for your answer. Is this a planned feature to add parameters to <*Package> installCommand ? Gilles On Tue, Dec 20, 2011 at 7:31 PM, Ian Williams wrote: > Command line variables given to the bundle are passed to the BA. The > WixStdBA currently does not turn them into variables that you can use in your > bundle. > > -Original Message- > From: Gilles QUERRET [mailto:g.quer...@gmail.com] > Sent: Tuesday, December 20, 2011 7:11 AM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Burn and variables > > Hello, > > > I'm using burn to create an install bundle, and I'd like to pass variables > from the command line to ExePackage InstallCommand. A shortened version of my > WXS file is : > > > > I'm using "MyBundle.exe MYVAR=foo /quiet" to install the bundle, but > when using process explorer, setup.exe is never thrown with my variable set. > Is there something wrong in the InstallCommand syntax ? Or in the > MyBundle.exe command line ? > > > Thanks a lot ! > > -- > Gilles QUERRET > > -- > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create new > or port existing apps to sell to consumers worldwide. Explore the Intel > AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > -- > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Gilles QUERRET Riverside Software 15d route de Bellevue • 69440 Mornant • France Mob : +33 662.525.532 -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn and variables
Hello, I'm using burn to create an install bundle, and I'd like to pass variables from the command line to ExePackage InstallCommand. A shortened version of my WXS file is : I'm using "MyBundle.exe MYVAR=foo /quiet" to install the bundle, but when using process explorer, setup.exe is never thrown with my variable set. Is there something wrong in the InstallCommand syntax ? Or in the MyBundle.exe command line ? Thanks a lot ! -- Gilles QUERRET -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Problem creating shortcut
Hi, I have a problem in my installer with creating shortcuts : basically, I need to create a shortcut where the executable isn't part of my installer and I just need to provide parameters. I retrieve the executable path using : And I add icon using : http://localhost/foo/bar"/> Problem is that when running the installer, I get my icon created in desktop folder, but executable path isn't the value of PROWCINI_PATH, but to its parent directory. WiX help says for target attribute that the value will be defaulted to the parent File when nested under a File element. So how is it possible to create a shortcut using the correct executable path ? Best regards -- Gilles QUERRET - 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
Re: [WiX-users] Problem creating shortcut
Hi, Thanks for your answer. Changing to [PROWCINI_PATH] didn't work at first glance, so after deeper investigations, I found the value returned by RegistrySearch wasn't correct. Changing attribute Type to "raw" (and removing $ sign before PROWCINI_PATH ! ) gives me a correct result. So I now have a working solution, but is it normal that using attribute Type="file" gives me an incorrect result (I get parent directory instead of file name) ? Best regards Gilles QUERRET -Message d'origine- De : Mike Dimmick [mailto:[EMAIL PROTECTED] Envoyé : mardi 3 octobre 2006 11:28 À : Gilles Querret; wix-users@lists.sourceforge.net Objet : RE: [WiX-users] Problem creating shortcut The $ symbol is used in the Target attribute to find a component's path. You need to evaluate the value of the property, so your Target should be [PROWCINI_PATH]. References: Shortcut table: http://msdn.microsoft.com/library/en-us/msi/setup/shortcut_table.asp Shortcut data type: http://msdn.microsoft.com/library/en-us/msi/setup/shortcut.asp Formatted data type: http://msdn.microsoft.com/library/en-us/msi/setup/formatted.asp -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gilles Querret Sent: 03 October 2006 08:06 To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] Problem creating shortcut [2nd try, first one never appeared on mailing list] Hi, I have a problem in my installer with creating shortcuts : basically, I need to create a shortcut where the executable isn't part of my installer and I just need to provide parameters. I retrieve the executable path using : And I add icon using : http://localhost/foo/bar>"/> Problem is that when running the installer, I get my icon created in desktop folder, but executable path isn't the value of PROWCINI_PATH, but to its parent directory. WiX help says for target attribute that the value will be defaulted to the parent File when nested under a File element. So how is it possible to create a shortcut using the correct executable path ? Best regards -- Gilles QUERRET - 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
[WiX-users] Problem creating shortcut
[2nd try, first one never appeared on mailing list] Hi, I have a problem in my installer with creating shortcuts : basically, I need to create a shortcut where the executable isn't part of my installer and I just need to provide parameters. I retrieve the executable path using : And I add icon using : http://localhost/foo/bar>"/> Problem is that when running the installer, I get my icon created in desktop folder, but executable path isn't the value of PROWCINI_PATH, but to its parent directory. WiX help says for target attribute that the value will be defaulted to the parent File when nested under a File element. So how is it possible to create a shortcut using the correct executable path ? Best regards -- Gilles QUERRET - 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
