I am using Wix 3.6 Burn to install an Adobe Air application. The way it
works is that I call Adobe's arh.exe tool with the path to the app.air file to install. I use an ExePackage element for arh.exe and a Payload element for app.air. Now I need the full path to payload. How do I retrieve it? A relative path would also have worked, except that the working folder is set to installer's location. <ExePackage SourceFile = "arh.exe" InstallCommand = "-installAppSilent [Payload path goes here]" UninstallCommand = "-uninstallAppSilent MyApp" PerMachine = "yes" > <Payload SourceFile = "MyApp.air" Compressed = "yes" /> </ExePackage> ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: BUILD Helping you discover the best ways to construct your parallel projects. http://goparallel.sourceforge.net _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
There is a bug tracking that feature request.
On Sun, Dec 2, 2012 at 7:10 PM, Don Reba <[hidden email]> wrote: > I am using Wix 3.6 Burn to install an Adobe Air application. The way it > works is that I call Adobe's arh.exe tool with the path to the app.air file > to install. I use an ExePackage element for arh.exe and a Payload element > for app.air. Now I need the full path to payload. How do I retrieve it? > > A relative path would also have worked, except that the working folder is > set to installer's location. > > <ExePackage > SourceFile = "arh.exe" > InstallCommand = "-installAppSilent [Payload path goes here]" > UninstallCommand = "-uninstallAppSilent MyApp" > PerMachine = "yes" > > > <Payload > SourceFile = "MyApp.air" > Compressed = "yes" > /> > </ExePackage> > > > > > ------------------------------------------------------------------------------ > Keep yourself connected to Go Parallel: > BUILD Helping you discover the best ways to construct your parallel > projects. > http://goparallel.sourceforge.net > _______________________________________________ > WiX-users mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching http://RobMensching.com LLC ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: BUILD Helping you discover the best ways to construct your parallel projects. http://goparallel.sourceforge.net _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
Thanks. Is there a straightforward way of doing this using current
functionality? "Rob Mensching" wrote in message news:CAHdHTVeT_cHdxDmtPm_1PCLioL9nydOGajHDvDFLhbaKXhR=[hidden email]... There is a bug tracking that feature request. On Sun, Dec 2, 2012 at 7:10 PM, Don Reba <[hidden email]> wrote: > I am using Wix 3.6 Burn to install an Adobe Air application. The way it > works is that I call Adobe's arh.exe tool with the path to the app.air > file > to install. I use an ExePackage element for arh.exe and a Payload element > for app.air. Now I need the full path to payload. How do I retrieve it? > > A relative path would also have worked, except that the working folder is > set to installer's location. > > <ExePackage > SourceFile = "arh.exe" > InstallCommand = "-installAppSilent [Payload path goes here]" > UninstallCommand = "-uninstallAppSilent MyApp" > PerMachine = "yes" > > > <Payload > SourceFile = "MyApp.air" > Compressed = "yes" > /> > </ExePackage> ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: BUILD Helping you discover the best ways to construct your parallel projects. http://goparallel.sourceforge.net _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
In reply to this post by Don Reba
My solution to this problem was to write a helper executable that launched
whatever command it was given as an argument within the folder in which it was placed. <ExePackage SourceFile = "$(var.Launcher.TargetPath)" InstallCommand = 'arh.exe "-installAppSilent MyApp.air"' UninstallCommand = 'arh.exe "-uninstallAppSilent MyApp"' PerMachine = "yes" Vital = "yes" > <Payload SourceFile = "arh.exe" Compressed = "yes" /> <Payload SourceFile = "MyApp.air" Compressed = "yes" /> </ExePackage> ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
This post has NOT been accepted by the mailing list yet.
just an FYI, I know this is a really old thread, but I came across it on nabble while trying to figure this out, so for anyone else landing here, as of at least 3.11, there is now a wix variable you can use to get the payload path, so no custom action needed, WixBundleExecutePackageCacheFolder
Here is an example of me using it with an ExePackage: (also note & quot; this folder may have spaces in it, so you need to wrap it in quotes) <ExePackage Name="Zebra_CoreScanner_Driver_(64bit)_v3.00.0003.exe" Id="ZebraBarcodeScanner" SourceFile="Resources\Zebra_CoreScanner_Driver_(64bit)_v3.00.0003.exe" PerMachine="yes" DetectCondition="SCANNERINSTALLED = 1" InstallCommand="/s -f1"[WixBundleExecutePackageCacheFolder]setup.iss"" UninstallCommand="/s -f1"[WixBundleExecutePackageCacheFolder]uninstall.iss"" DisplayName="Zebra Barcode Scanner" > <Payload Name="setup.iss" SourceFile="Resources\setup.iss" Id="ZebraCoreSetupisss" /> <Payload Name="uninstall.iss" SourceFile="Resources\uninstall.iss" Id="ZebraCoreuninstalliss" /> </ExePackage> |
Free forum by Nabble | Edit this page |