> From: Rob Mensching
>To: General discussion about the WiX toolset.
>
>Sent: Wednesday, May 21, 2014 3:55 PM
>Subject: Re: [WiX-users] [WiX-devs] Query- Wix 3.5 integration with VS 2013
>
>
>And that technically isn't necessary. You'll just get a warning saying the
>RegistryKey/@Action attri
And that technically isn't necessary. You'll just get a warning saying the
RegistryKey/@Action attribute is deprecated.
I too am curious why upgrading is a big deal. We work hard to maintain
backwards compatibility in the minor version updates.
__
If you look at HandleExitCode at the bottom of exeengine.cpp (
https://github.com/wixtoolset/wix3/blob/develop/src/burn/engine/exeengine.cpp),
you'll see that the engine doesn't set hrStatus in ExecutePackageComplete
to the exit code. It always returns S_OK unless the EXE package's exit
code trans
I just did this and it was pretty painless. Only had to make one change to my
wxs - remove the 'Action="create"' attribute from my RegistryKey element.
Dave
>
> From: Heath Stewart
>To: General discussion for Windows Installer XML toolset.
>; Windows Installe
This worked for me:
-Original Message-
From: Tom Brezinski [mailto:to...@networkinstruments.com]
Sent: Wednesday, May 21, 2014 7:12 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Burn StandardBA Dynamic Laun
Is there a way to change the StandardBA LaunchTarget based on a user selection?
I have the following 4 radio buttons in my bundle which determine which
features I install:
Depending on which the user selects I want LaunchTarget to be different. For
example i
Hi Team,
We are creating one application for which we have applied a
check of .net framework 4.0 to be installed on the system in MSI. Presently it
successfully displays the user a message and exits if framework 4.0 is not
installed on the users machine.
But we wanted to give use
Use Burn. Both Visual Studio and SSDT installer use it to download a lot of
stuff during their installs. It is designed for this scenario.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@
There is none, it is not supported. I would recommend using WiX 3.8.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Shri
Hello,
I am writing a custom managed BA to be used with my Burn bootstrapper. The
chain to install consist of several EXEs, with various return codes that I have
mapped to Burn behaviors (success, reboot required, error, ...) using
.
When one of the EXE packages fails, Burn detect the failure
Hi,
This is in regards with WIX 3.5 integration with VS 2013. Currently we have Wix
3.5 integration with VS 2010 but not with VS2013, although we can integrate the
latest Wix version 3.8 with VS2013 , but doing so result lot of modification in
existing tools and require rigorous testing efforts
Just for info. There seems to be an issue when installing NetFx 4.5.2 on
Win 7 x64 Enterprise RTM:
http://wixtoolset.org/issues/4416/
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-8-Installer-and-NetFx-4-5-2-on-Win7-x64-td7594631.html
--
12 matches
Mail list logo
