Straight from the tutorial: "The term NOT (!FeatureName = 3) means the feature
is not installed locally."
So since I want the install to stop if the feature *is* already installed in my
product.wxs I have:
Problem is this *always* stops the installer even when the software is not
ins
>It's a cliché but... I can imagine Rob saying/thinking "Do you know who I
>am!?" Of course, Rob would never actually say or think anything like that. ;-)
Well I could say the same about myself and I think most first time visitors to
WiX could as well. For the most part we're fairly experienced
Bingo! I haven't looked at this yet, but it looks like it might be what I'm
looking for. FYI I am using radio buttons, but the choice of controls isn't the
crux of this issue.
Thank you for finding this!
Greatly appreciated.
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:
set.
I wish you good luck on your path to understanding declarative installation.
On Thu, Jul 28, 2011 at 4:13 PM, Peter Stein wrote:
> Not sure why this is so difficult to understand. The installer has
> components that are safe to install in some environments/contexts but
> not in others.
ponents which
then roll up into Feature costing. As you turn Features on and off, the costing
will be adjusted.
On Thu, Jul 28, 2011 at 1:01 PM, Peter Stein wrote:
> I don't understand all of your explanation starting with "The key here...".
>
> I get what you are saying ab
My mistake was to try altering ADDLOCAL directly. Or so I now think. Apparently
the correct way to do this is by publishing an AddLocal event, i.e. 1.
I tried to follow an example from the N. Ramirez book, but it doesn't seem to
work. Here's the email I sent to Nick, but if anyone else has an i
translates into "do things the Windows Installer
way". Note that I didn't say "WiX way" and there's a very good reason for that.
You *will* spend months trying to accomplish something that actively tries to
sabotage how Windows Installer works, but that's your
re selection
dialog that lets you configure directories...
Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
> -Original Message-
> From: Peter St
installed is a *very bad* design. You'll end up in an immediate
> "repair" state that has real potential of creating problems for you all over
> the place later.
>
> ...or maybe I just don't really understand the scenario.
>
> On Thu, Jul 28, 2011 at 7:44 AM,
gets removed.
If you don't want filexyz.exe in the product then just don't put it in your
upgrade. Once you get the upgrade really working with RemoveExistingProducts,
if it's not being removed then something else is going on (clobbered ref
counts, marked permanent etc).
Phil
I based my code on this:
http://stackoverflow.com/questions/3287626/wix-installer-remove-files-on-uninstall-but-not-on-upgrade
I saw no complaints about the suggested answer so I assumed it worked. But when
I adapted to my code it does nothing.
In product.wxs:
1
And in my main installa
. Which in turn means ADDLOCAL
cannot be used because of my previous findings. I think it may be time for a
brute force solution like including a helper app in the installer.
-Original Message-
From: Peter Stein [mailto:pst...@instec-corp.com]
Sent: Wednesday, July 27, 2011 1:48 PM
To
My installer has a dialog that lets the user choose a feature. Based on that
choice ADDLOCAL is modified via a custom action.
The problem seems to be that WiX has insufficient granularity with regards to
scheduling UI actions. The problem I can't seem to solve is precisely how to
schedule this
k you Bob & Rob.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Wednesday, July 13, 2011 10:31 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] can't eliminate Error 2343 for InstallDirDlg.wxs in
Toolset 3.5
On 12-Jul-11 10:54, Peter Ste
't rooted in TARGETDIR/SourceDir?).
[PS] - I don't think so here's the directory structure:
On Tue, Jul 12, 2011 at 7:54 AM, Peter Stein wrote:
> I apologize if this email appears to be a duplicate. Although I'm
&
I apologize if this email appears to be a duplicate. Although I'm registered my
previous email was deleted.
It seems I can't get rid of this 2343 Error no matter how I set the
WIXUI_INSTALLDIR property. As an experiment I created an installer that only
contains a Product.wxs which only loads th
16 matches
Mail list logo
