Due to lack of foresight and inexperience when I was new to WiX, I've gotten
myself the following problem:
I have 2 product installers, A & B. Each contains 2 DLLs, X & Y.
A always installs both X & Y to folder M
B (optionally) installs X to M and Y to another folder, N
A is a released product a
A client wants to run our (StdBA) installer silently from a batch file and
detect whether or not the installation was successful. Would I be right in
thinking the exit code will be zero on success and non-zero on failure? If
not, what's the best way to determine if the installation succeeded?
For the record and the benefit of future generations, I overcame my problem by
switching from using
True
False
True
Sources;Content
DSV-Testing.xslt
--
Date: Wed, 19 Feb 2014 16:02:07 +
From: "Parkes, Kevin"
I'm trying to include a "sample" C# project in my installer using HeatProject
as follows:
The output file, _DVSDemo.wxs, is being created but apparently not compiled and
included in the installer, leading to "Unresolved reference" errors for the
component groups in _DVSDemo.wxs.
What
I'm using a custom theme with WixStandardBootstrapperApplication and my
elements look a bit rubbish. I've tried various combinations of Height, Weight
and font name and, while some look worse than others, none seems to me to look
particularly good. Could I be doing something wrong? Any tricks/t
I am replacing a (very) old Visual Studio installer project with WiX.
I've copied the UpgradeCode from the old installer and have remove existing
products scheduled after install validate but I am seeing slightly odd
behaviour if I upgrade from old to new and subsequently uninstall: some DLLs
a
I need to install a file into the 64-bit Program Files folder from a 32-bit MSI.
I know it's bad form, but it's a config file for something else which probably
ought to be reading config files from somewhere more neutral, but that's beyond
my control.
I've tried using a with Path="[%ProgramFil
Is it possible to restart (ie stop and then start) a service (*not* installed
by the MSI) using or would it require a custom action?
(The MSI installs a configuration file for the service in question, which must
be restarted for the new settings to take effect.)
Thanks
Hi Phill
Unfortunately the per-user version of CommonFilesFolder requires Windows
Installer 5.0 (Win 7) and, even more unfortunately, we still have to support
XP. What you have does indeed build without warnings but, unless you explicitly
run msiexec elevated, the per-user installer fails with
MachineMSI.wxs
Thanks
Kevin
-Original Message-
From: Parkes, Kevin
Sent: 27 June 2013 17:02
To: 'wix-users@lists.sourceforge.net'
Subject: Re: per-user/per-machine in MSM, MSI and bundle
>Are the components that are flagged by those two
>Are the components that are flagged by those two ICE warnings coming from the
>MSM or from the MSI consuming it?
The components are in the MSM but the warnings appear when building the MSI
>What resources are in the components producing the ICE 57 warnings?
It is just one component (gene
Question 1.
I am creating an MSM for a COM DLL. I am using the MSM in my own per-user MSI
and I am getting ICE warnings 57 ("per-user and per-machine data with an HKCU
Registry KeyPath") and 91 ("file will be installed to the per user directory
that doesn't vary based on ALLUSERS "). How do I fi
ntent-Type: text/plain; charset=UTF-8
1. Make sure your Bundle's MsiPackage element is cached (i.e. do not add
Cache='no').
2. Make sure the MSI has the same name. (
http://blogs.msdn.com/b/robmen/archive/2004/12/08/278746.aspx)
On Tue, Mar 26, 2013 at 9:20 AM, Parkes, Kevin
We have an MSI which successfully installs as part of bundle. So far, so good.
We need to be able to run the same MSI from another, non-WiX (long story, don't
ask) installation bootstrapper. On its own, this also works. However, if we
run this 2nd installer after the WiX bundle, the MSI fails t
Apart from the former being easier to add in project properties, what would be
the pros and cons of using project Pre-build Events compared to & ?
--
Everyone hates slow websites. So do we.
Make your web apps faster wit
Thanks Neil, I suspected as much. In this instance the message isn't vital so
I'll just do without it. (I dare say it would be useful to others - probably
including me in the future.)
Kevin
-Original Message-
Date: Mon, 26 Nov 2012 14:55:13 +
From: Neil Sleightholm
Subject: Re: [W
I'm using the standard BA with a custom theme in which I've added a short
message to the Success page. Unfortunately the same page is also used for
successful uninstall when the message isn't relevant. Is it possible to hide or
change text conditionally depending on whether install or uninstall
t sure) and also the signtool can
> hold on to the file. I have ended up with a few sleep operations after
> each step - not ideal but has made the build more reliable.
>
> Note sure this helps.
>
> Neil
>
> -Original Message-
> From: Parkes, Kevin
I've set to true and added
and
to my VS project (each using to run a batch file we use for signing)
Frequently, project build is failing (at least 2 times out of every 3 ) with
access denied errors from either LINK or in the batch file. It would appear VS
isn't waiting for one thing to f
API) would all call the same underlying code to perform the driver install.
Seems like anything else would be a crazy design.
> -Original Message-
> From: Parkes, Kevin [mailto:kevin.par...@wacom.eu]
> Sent: Friday, November 16, 2012 15:29
> To: wix-users@lists.sourceforge.net
I'm trying to replace a driver "installer" (essentially a self-extracting EXE
with INF file etc. which runs DPInst) with a WiX-based MSI.
I'm using WixDifxAppExtention and it's working except that I get a security
warning: "Windows can't verify the publisher of this driver software" (with
optio
If I update my installer to include a new version of a .Net assembly, should I
change the guid of the component containing the DLL?
Thanks
--
Live Security Virtual Conference
Exclusive live event will cover all the ways t
be that data.
Some tools (like Visual Studio setups) hide these internal details, can't
remember if WiX does.
Phil W
-----Original Message-
From: Parkes, Kevin [mailto:kevin.par...@wacom.eu]
Sent: Friday, March 09, 2012 9:23 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-us
I have a couple of deferred custom actions to which I need to pass parameters.
Obviously for a single custom action I'd just set the CustomActionData
property. Do I have to pack all parameters for each custom action into
CustomActionData and have each action extract its own parameters somehow or
Is it possible to set the font used for edit controls? (I'd like to make one
fixed pitch). I know you can use, eg, Text="{\WixUI_Font_Normal}..." for text
controls but this doesn't appear to work for edit controls.
Thanks
--
My installer includes a pair of DLLs each with a set of MUI localization files.
Each of the DLLs is generating a warning on the element:
ICE03: String overflow ... Table: File, Column: Language
When I look at the resulting file table in Orca, I can see each of the language
IDs for the MUI fi
I'm exploring Burn and would like to try using my own theme with
WixStandardBootstrapperApplication.Foundation. I'm probably being dense but I
haven't managed to get anything working so far and the documentation isn't
exactly extensive (yet).
A few quick pointers as to how to get started would b
checkbox in the main bit of the dialog without the grey background?
-Original Message-
From: Parkes, Kevin [mailto:Kevin.Parkes@...]
Sent: Tuesday, January 24, 2012 9:45 AM
To: wix-users@...
Subject: [WiX-users] Run App After Setup
I want to run an installed app after setup completes. I've
I want to run an installed app after setup completes. I've seen the "How to..."
on the subject, but that doesn't seem to allow for passing command line
arguments to the app, which I need to do. How can I run the app with command
line arguments? (My installer creates a shortcut, with the required
t/plain; charset="us-ascii"
The actual case-sensitive property name is SourceDir:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa371857(v=vs.85).aspx
SOURCEDIR is likely to be something internal that you should not be using.
Phil Wilson
-----Original Message-
F
R] delayed in silent install, and can I force it to be
set sooner? Alternatively is there another way to test for folder
[SOURCEDIR]\ABC later than AppSearch? (I simply want to copy the folder and its
contents, if they exist, to the target directory.)
-Original Message-----
From: Parkes, K
sequences in Orca/InstEd ?
-Original Message-
From: Parkes, Kevin [mailto:Kevin.Parkes@...]
Sent: 29 November 2011 15:33
To: wix-users@...
Subject: Re: [WiX-users] Directory and Registry Search failing in silent mode
I don't think it should be anything to do with user's profile: the
the log say the values of SOURCEDIR and ALLUSERS are in the
property dump(s) at the end ?
-Original Message-
From: Parkes, Kevin [mailto:Kevin.Parkes@...]
Sent: 29 November 2011 15:33
To: wix-users@...
Subject: Re: [WiX-users] Directory and Registry Search failing in silent mode
I
ge/InstallScope set to
perUser ? Are you using MSI 5 or something earlier ?
-----Original Message-
From: Parkes, Kevin [mailto:Kevin.Parkes@...]
Sent: 29 November 2011 14:20
To: wix-users@...
Subject: [WiX-users] Directory and Registry Search failing in silent mode
I have properties set by a
I have properties set by a and a both of
which work as expected with UI but neither of which is set when run in silent
mode:
Log file with UI:
Action start 11:29:54: AppSearch.
AppSearch: Property: DOTXYZ, Signature: DotXYZSearch
MSI (c) (D0:A4) [11:29:54:650]: Note: 1: 2262
I am using WixDifxAppExtension to install a printer driver as part of an
application installer. The WiX source is as follows:
The corresponding custom actions apparently complete successfully. However, the
install log file includes the lines:
36 matches
Mail list logo