I just figured out how this works looking through the WixStdBA source code.

This was implemented in time for the RC release on May 21. 
(https://sourceforge.net/tracker/index.php?func=detail&aid=3489809&group_id=105970&atid=642714)

To pass command line arguments, it goes something like this:

<Wix>
<Bundle>
    <Variable Name="CommandLineArg" bal:Overridable="yes"/>
    <Chain>
      <MsiPackage>
        <MsiProperty Name="CommandLineArg" Value="[CommandLineArg]"/>
      </MsiPackage>
    </Chain>
</Bundle>
</Wix>

You have to make a bundle variable that is overridable at the command line and 
then pass that variable to your msi.


Re: [WiX-users] Pass parameters from bootstrapper to msi bundle 
package<https://sourceforge.net/mailarchive/message.php?msg_id=29237310>
From: Hoover, Jacob <Jacob.Hoover@gr...> - 2012-05-09 03:13


Assuming you are using the StdBA, I am mostly certain that the passing

of bootstrapper params to the underlying packages has not been

implemented. Sadly, the native BA is a bit rough around the edges. For

now the "team" has been focusing on the core functionality of burn and

not the BA's. My advice would be if you need a BA now then it would be

faster to do in a MBA than a BA (if your application already requires

.Net). If you can't swallow .Net as a prereq, then I'd suggest forking

on codeplex and adding the functionality you are looking for.



-----Original Message-----

From: Tomislav Markovski [mailto:tmarkovski@...]

Sent: Tuesday, May 08, 2012 10:56 AM

To: wix-users@...

Subject: [WiX-users] Pass parameters from bootstrapper to msi bundle

package



I'm using VS2010 and WiX 3.6 to create MSI packages and bundle them into

Bootstrapper setup. Here's my Boostrapper code.



<?xml version="1.0" encoding="UTF-8"?>

<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";>

    <Bundle Name="" Version="" Manufacturer="" UpgradeCode="">

        <BootstrapperApplicationRef

Id="WixStandardBootstrapperApplication.RtfLicense" />



        <Chain>

              <MsiPackage SourceFile="Package1.msi">

                <MsiProperty Name="PARAM1" Value="[PARAM1]" />

                <MsiProperty Name="PARAM2" Value="[PARAM2]" />

              </MsiPackage>

              <MsiPackage SourceFile="Package2.msi">

                <MsiProperty Name="PARAM1" Value="[PARAM1]" />

                <MsiProperty Name="PARAM2" Value="[PARAM2]" />

              </MsiPackage>

        </Chain>

    </Bundle>

</Wix>



The MSI packages must have the parameters specified in order to run.

Normally, I would call "Packag21.msi PARAM1=1 PARAM2=2". After I build

the project, I try to pass the parameters to my Bootstrapper.exe in the

same manner Bootstrapper.exe PARAM1=1 PARAM2=2, but it doesn't seem to

pass them to the MSI. Installations hang with the missing parameters

condition.



Is there a way to pass the parameters from the exe to the msi?

------------------------------------------------------------------------

------

Live Security Virtual Conference

Exclusive live event will cover all the ways today's security and threat

landscape has changed and how IT managers can respond. Discussions will

include endpoint security, mobile security and the latest in malware

threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________

WiX-users mailing list

WiX-users@...

https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to