I checked the source code of WIX 3.X, in the following file
https://github.com/wixtoolset/wix3/blob/develop/src/burn/engine/registration.cpp
if you look at the lines 725,726, it contains the following:
// InstallLocation: provided by UI
// TODO: need to figure out what "InstallLocation"
Extend the firewall custom action to support it?
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: John Mellor [mailto:jmel...@blackberry.com]
Sent: Thursday, July 1
Sounds like a bug. Burn should allow you to set that value if it's going to be
required by Windows. Is that requirement written down somewhere? If so, it'd be
great to link to it in the bug.
___
FireGiant | Dedicated support for the
Look at the examples at https://wixextba.codeplex.com/documentation
The code at this site was downloaded for wix 3.7, but for wix 3.8 and later
most of it is available by using the built in features and the sample
BAFunctions project. Implement code in the BAFunctions project to detect
the prerequ
Yes.
True
..\packages\Microsoft.Web.Administration.7.0.0.0\lib\net20\Microsoft.Web.Administration.dll
The True inside the reference is what you need.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 9
I apologize for not reading your question carefully in the other thread. Did
you try to set CustomAction/@Impersonate="yes"?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSI-runs-an-EXE-and-it-cannot-write-to-a-file-in-programdata-folder-in-win
I have a bootstrapper application which has two packages, .NET framework as
pre-requisite and the actual component as another package. The entire
installation works fine including the pre-requisites, there is theme file
that's been created to define the wizards.
The first screen in the wizard dis
I am trying to get a certain package to run when the user launches the
uninstall but not when the bundle is removed by a related bundle that is
upgrading it. I tried adding "NOT WixBundleAction = "4"" to my
DetectCondition but that doesn't work. Is there a way for a package to
distinguish if the bu
Indeed - this is pretty much the conclusion we've come to - managing
features felt like a rabbit hole down which we didn't want to disappear!
Thanks for you comments.
Tom
On 17 July 2014 00:05, Rob Mensching wrote:
> I should also note that manipulating Feature states is way more
> challengin
Hello all,
if say briefly, I have a script with next parts:
/ //
// //
// //
// //
//
// //
// //
// //
// //
//
// //
// NOT (Installed) AND NOT (PREVIOUSVERSIONSINSTALLED OR
NEWERVERSIONDETECTED)//
// //
// //
// NOT (Installed) AND NOT (PREVIOUSVERSIONSINSTALLED
10 matches
Mail list logo