Hello all,
We had a build machine which used to install Wix3.6 msi using
msiexec /qr /i WiX\wix36.msi
Now, we are updating our build scripts to use Wix37.exe , but I dont know is
there a way to install latest wix using command line ?
Are there any options with this exe so that i can silent ins
okay that worked. But now I want to uninstall wix37.exe since its not a
stable release and use wix3.6 as the stable one.
Uninstalling wix37.exe from Control Panel says "failed to uninstall - try
again"
I tried using Wmic command like :
wmic product where name="WiX Toolset v3.7 Core" call uninst
[update]I restarted my machine and uninstallation went well.
Anyways, which log file are we referring here ?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Install-Wix37-exe-using-command-line-tp7580153p7580296.html
Sent from the wix-users maili
Hello all,
We already have a big size msi for our product and it supports installation
of various features. Now, with Wix3.6 onwards, we want to use Burn in our
build stage.
My main concern before moving to Burn is that :
- how would I know if my current MSI needs Burn supported functionality or
I have read the documentation of from source code. I couldn't get a
simple burn example worked out.
My bundle.wxs file is:
http://schemas.microsoft.com/wix/2006/wi";>
I am using wix3.6.exe on my machine.
The log file is all I have. Actually i googled the problem before posting
here and ran into one thread (similar to this problem) where you only
replied asking for "msbuild -fl " output. Hence I attached that output.
--
View this message in context:
http:
been lost. Can you provide all the error
> information from the log file directly in the email?
>
> On Mon, Sep 10, 2012 at 9:51 PM, vchauras <[hidden
> email]<http://user/SendEmail.jtp?type=node&node=7580415&i=0>>
> wrote:
>
> > I am using wix3.6.exe
;FindUnderPath"
Comparison path is "bin\Debug\".
Done executing task "FindUnderPath".
Task "FindUnderPath"
Comparison path is "obj\Debug\".
Done executing task "FindUnderPath".
Task "RemoveDuplicates"
Done executing task "RemoveDuplic
Hello all,
I have following snippet in Bundle.wxs
When I build and run my exe, it does NOT give the UI and installation
doesn't work.
ht.xml
http://wixtoolset.org/schemas/thmutil/2010";>
#(loc.Captio
Hello all,
I want to know if there are any guidelines (best practices) to care about
before clubbing 2 MSI s together using burn. For e.g. I have m1 and m2 as
two msi s.
Both the msi have their own LaunchConditions (which may overlap) where they
check before install (like .NET framework version,
I am getting this error in log file.
===
[28F8:28F0][2012-09-14T12:17:11]: Setting string variable 'WixBundleName' to
value 'my_Bootstrapper2'
[28F8:2E30][2012-09-14T12:17:11]: Error 0x80070002: Failed to probe for loc
file: thm.wxl in path:
C:\Users\VCHAUR~1\AppData\Local
Yes, I want a single unified installation. The flow of UI would be something
like:
1- Welcome
2- Ask for user inputs (checkbox, filling some values)
3- The user inputs can now be passed to m1 and m2 if they need that specific
info
4- m1 runs with its input
5- m2 runs with its input
6- finish
I wr
I wasn't able to resolve this issue for now, but I think it should be
trivial; so leaving it as it is.
Doubt 1: Can I change the theme file to show checkboxes/form fields where
user can feed in data which can be set as Properties and used in
installation later ?
Doubt 2:
If [Doubt 1 == No] , then
Hello all,
My need to develop is custom UI is as follows:
1. - I want the user to select which msi to install (using checkbox)
2. - Depending on which msi user selects , my next UI page would be get more
information from the user needed for the selected MSI.
So, have googled about this , I found
look at WixBA\Bundle.wxs file where authors declare "InstallFolder" as string
variable and they set that variable
within the WixBA.cs code like:
this.Engine.StringVariables["InstallFolder"] = XYZ.
This is the way in which burn relays params to msipackage.
--
View this message in context:
ht
Yes I know, but I wanted to pass the value as a parameter which
should be set by Burn engine. Hence I did it that way.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Set-and-pass-a-variable-or-something-similiar-when-a-feature-is-selected-tp75799
There is one here
http://bryanpjohnston.wordpress.com/2012/09/28/custom-wix-managed-bootstrapper-application/comment-page-1/#comment-7
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Examples-of-Burn-tp7578587p7580985.html
Sent from the wix-users
Burn based codes have a bootstrapper C# code too.
On Mon, Oct 1, 2012 at 8:11 PM, Katherine Moss [via Windows Installer XML
(WiX) toolset] wrote:
> I don't get it; aren't WiX projects written purely in XML?
>
> -Original Message-----
> From: vchauras [mailto:[hidden
18 matches
Mail list logo