Hi,
How do I use a property set to RadioButton in a Feature condition?
I have a Secure property called UNICODETYPE which gets set to the value of
radio button selection.
I want to use that property to decide which feature to install.
Do the Level of parent feature matter, note it is 200. My und
t.com/
-Original Message-
From: Skildum, Mat [mailto:mathew.skil...@aspect.com]
Sent: Wednesday, June 25, 2014 8:11 AM
To: General discussion for Windows Installer XML toolset.
(wix-users@lists.sourceforge.net)
Subject: [WiX-users] Feature getting set to advertise for maintenance
I am seeing a
I am seeing a weird behavior where a feature that was installed locally is
getting set as advertised when a repair or patch is run against the product. I
have never seen this behavior before and have not been able to find a solution
or a cause.
In the installation the features are all set as a
So the components in FeatureC can be installed as a standalone feature, but
those same components are needed by Features A and B?
I'd just include the components in all three features. And don't nest
Feature C inside Feature A or B.
--
View this message in context:
http://windows-installer-xml
toolset.
Subject: Re: [WiX-users] Feature request
I think rebasing a wixpdb is a great feature request. If it hasn't already been
filed, please add one.
Blair
From: Tunney, Stephen
Sent: Thursday, December 12, 2013 11:57 AM
To: General discussion for Windows Installe
After you file the feature request, please discuss it with us on wix-devs. I’m
wondering if melt is the best place to rebase a wixpdb and I think we should
discuss the use cases and workflows before you work on the changes.
-Blair
From: Bob Arnson
Sent: Sunday, December 15, 2013
On 12-Dec-13 14:52, Tunney, Stephen wrote:
> Can melt simply "rebase" the wixpdb if I were to point it to an already
> existing melt output directory? I basically don't want to have melt
> re-output everything to the -x argument again. Nothing on the help syntax
> for 3.7 indicates a way of do
I think rebasing a wixpdb is a great feature request. If it hasn't already been
filed, please add one.
Blair
From: Tunney, Stephen
Sent: Thursday, December 12, 2013 11:57 AM
To: General discussion for Windows Installer XML toolset.
Hello all,
Ok, I finally have Pure Wi
Hello all,
Ok, I finally have Pure WiX Patching working on my projects. I have a small
issue though.
Melting all of our "RTM" products takes about 35 minutes to complete. What I
have found is that if I zip up this collection of goodies and stick it on the
network share ONCE, I can copy it do
Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Thursday, December 5, 2013 9:51 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Feature based MSI and Boostrapper question... [P]
Classification: Public
I wasn't expecting the BA to show the UI for feature selection.
So what
--Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: December-06-13 12:24 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Feature based MSI and Boostrapper question...
Currently, the stock BA doesn't allow feature selection but you
id it.
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: Thursday, December 05, 2013 3:00 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Feature based MSI and Boostrapper question...
Hi all,
Quick question… I haven’t set this up yet but would like to know if
Hi all,
Quick question… I haven’t set this up yet but would like to know if it is
feasible first before doing the work…
My application’s MSI has 3 features”
1. Client app 1
2. Client app 2
3. Client app 3
There is a feature tree page so you can select which feature you want to
ins
I want my feature SelectionTree to behave like radioButtons... But I do not
know how to do it...
I can not use custom dialog with radiobuttons, because options in
RadioButtonsGroup depends on condition(if some software is installed)... it
is not possible to disable just some options(only whole rad
.sourceforge.net
> Date: Tue, 13 Aug 2013 18:50:58 -0700
> Subject: [WiX-users] Feature question
>
>
>
> Hi all,
>
> we deploy two MSIs to our customers which are almost identical.
>
> The only difference is that 4 executables are slightly different (also named
> di
Hi all,
we deploy two MSIs to our customers which are almost identical.
The only difference is that 4 executables are slightly different (also named
differently) - all
other files are the same. The 4 executables also differ in their menu & desktop
shortcuts.
Could we use the feature element
Hi all,
we currently produce 2 MSIs that differ only as follows:
4 executables included in both MSIs have different names and slightly
different functionality and also different menu & desktop shortcuts. All
other files are identical.
Could these be delivered in one MSI and the feature element b
t; Default="yes">
> Value="ConfirmInstallForm">
>
But this will not show ConfirmInstallForm
>Width="66" Height="18" Text="{\VSI_MS_Sans_Serif13.0_0_0}&Next >"
> TabSkip="no" Default=&q
From: os...@live.com
To: reesslin...@matthews.com.au
Subject: RE: [WiX-users] Feature Selection
Date: Wed, 3 Jul 2013 17:27:41 -0700
I've used various "home-grown" bootstrappers, embedded UI, and more recently
Burn with custom BAs.
From: reesslin...@matthews.com.au
To:
Not certain but do you need to publish AddLocal before you publish NewDialog?
> From: reesslin...@matthews.com.au
> To: wix-users@lists.sourceforge.net
> Date: Tue, 2 Jul 2013 23:16:15 +
> Subject: [WiX-users] Feature Selection
>
> I am have a simple problem connecting fe
I am have a simple problem connecting feature selection to a push button
I am have a strange problem with feature selection and a push button
discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Feature or Chained MSI?
Yes, see my previous comment.
On Wed, Dec 5, 2012 at 9:41 AM, Katherine Moss wrote:
> Doesn't bootstrapping cause problems for admins who are trying to
> deploy software via GPOs?
>
>
Wednesday, December 05, 2012 10:16 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Feature or Chained MSI?
>
> I would definitely consider using a Bundle for your scenario. I believe
> the world is moving (has moved?) to a place where .m
[WiX-users] Feature or Chained MSI?
I would definitely consider using a Bundle for your scenario. I believe the
world is moving (has moved?) to a place where .msi files are building blocks
stacked together and wrapped with a bootstrapper (Burn Bundles in WiX toolset).
You do need to think abou
GPO is a usually casualty when using Bundles. Automated deployments with
Bundles need to use something more powerful like System Center. I worried
about this much more before both Microsoft Office and Visual Studio moved
to a bootstrapper/bundle-like system.
On Wed, Dec 5, 2012 at 7:45 AM, Bruce
On 05/12/2012 15:15, Rob Mensching wrote:
> I would definitely consider using a Bundle for your scenario. I believe the
> world is moving (has moved?) to a place where .msi files are building
> blocks stacked together and wrapped with a bootstrapper (Burn Bundles in
> WiX toolset). You do need to t
I would definitely consider using a Bundle for your scenario. I believe the
world is moving (has moved?) to a place where .msi files are building
blocks stacked together and wrapped with a bootstrapper (Burn Bundles in
WiX toolset). You do need to think about the problem a little differently
when u
Hi,
It's really up to you, but there's a couple of things to consider:
* Would the reference data ever be installed without the main application?
* How do customers get hold of your application and the reference
data, and relevant updates?
* Have you looked at patching?
Normally, in your si
I am exploring moving a moderate size installer to WiX and I am stumbling
through with some good successes thanks to the active support community out
there. My application has a large amount (~1gb) of reference data that does
not change much from version to version. This data is not required f
Any suggestions for this issue?
On Fri, Oct 26, 2012 at 6:52 PM, Hans ter Horst wrote:
> Hello, I have a feature tree based installation, all working pretty well.
> The only issue is that when I have installed a subset of features and I
> want to add some more, the "Change" button is disabled wi
Hello, I have a feature tree based installation, all working pretty well.
The only issue is that when I have installed a subset of features and I
want to add some more, the "Change" button is disabled with the mention
that there are no independently selectable features in this install. I
don't see
If you enable feature selection (MsiPackage/@EnableFeatureSelection) then
Burn should fire callbacks on feature detection and planning.
Note: EnableFeatureSelection is off by default because managing feature
states in the Windows Installer can be very tricky.
On Tue, Dec 20, 2011 at 1:36 PM, shru
Hi,
Am using a bundled installer to install major upgrades for a bunch of MSIs
(that are installed using a bundle as well). While I can use
DetectRelatedMsiPackage event to be informed about a major upgrade, I
couldn't find a way to determine the state of individual features in the
previous instal
I think there is a topic in the WiX.chm that talks about how to do this.
On Fri, Sep 30, 2011 at 2:34 AM, Michael Tissington <
michael_tissing...@ciqual.com> wrote:
> I'm trying to launch an installed exe when the user clicks Exit, so I have
> the following but it NEVER launches the exe.
> What a
I'm trying to launch an installed exe when the user clicks Exit, so I have
the following but it NEVER launches the exe.
What am I missing?
(!MyFeature = 3) AND NOT (ACTION = "ADMIN")
--
All of the data generated in your
913-341-3434 x791011
jocoo...@jackhenry.com
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Saturday, August 06, 2011 9:54 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] feature install state always stops install under XP SP
Something is definitely fishy in there. Look at verbose log files for all
the different installs. They will show you the state of the Features and
from there you should be able to hunt down what is going on.
On Fri, Aug 5, 2011 at 9:36 AM, Peter Stein wrote:
> Straight from the tutorial: "The te
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
Hi,
I have some public properties in my Wix setup project. I am not using the
WixUI_FeatureTree. Instead I have checkboxes on my custom dialogs to set the
public properties which would later be used to set the level for a feature.
This works fine when I install using UI.
But, if I use silent ins
Hello all,
I am in need to add a Features tree with checkbox selection to my msi. Can
any one point me to some sample as how to achieve this.
Sincere thanks!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Feature-Tree-with-Checkbox-selection-tp59
ey [mailto:simon.top...@mwhsoft.com]
Sent: 26 January 2011 12:00
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Feature condition evaluation
I've gone down the repeated component ref's route and I'm happy with how it
works, it ref counts it correct
ork now is this checkbox, which seems to ignore the
components install or action state. More new as it comes.
Simon
-Original Message-
From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com]
Sent: 26 January 2011 11:49
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Fe
;Root', and 'Root' will be installed if any of 5 features will be installed).
But in this case you will need to show 'Root' feature to user.
Maksim
-Original Message-
From: Simon Topley [mailto:simon.top...@mwhsoft.com]
Sent: Wednesday, January 26, 2011 2:15 PM
igT>2
although I'm sure it won't work.. I'll try it.
-Original Message-
From: Simon Topley [mailto:simon.top...@mwhsoft.com]
Sent: 26 January 2011 10:14
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Feature condi
--Original Message-
From: Simon Topley [mailto:simon.top...@mwhsoft.com]
Sent: Monday, January 24, 2011 4:47 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Feature condition evaluation
Afternoon all,
SO I'm back trying to tackle this issue with my SetProp
onday, January 24, 2011 4:47 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Feature condition evaluation
Afternoon all,
SO I'm back trying to tackle this issue with my SetProperty after
Costfinalize. The property is set correctly, but nothing now seems to
r
Afternoon all,
SO I'm back trying to tackle this issue with my SetProperty after Costfinalize.
The property is set correctly, but nothing now seems to respond to it.
MSI (s) (3C:98) [04:37:53:630]: Doing action: SetCONFIGREQUIRED
Action 04:37:53: SetCONFIGREQUIRED.
Action start 04:37:53: SetCON
d Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Rune Moberg [mailto:jjfl...@gmail.com]
Sent: 23 January 2011 21:16
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Feature not pre-selected
I have a bunch of features. Some of th
I have a bunch of features. Some of them do not contain any file
resources, they're just there as a convenience to help the customer
get a few services up and running.
Given:
I expected that "MM2" would
Hello again all,
I thought I'd start a fresh topic as I now have a new issue. I set a property
to be "1" if a feature is being installed before "InstallValidate". The log
shows this property is being set correctly. I have 2 other features that are
hinged from this property that both don't get i
Thanks Vunder. I was using >= and I noticed in the url you supplied that they
used only = so tried &FeatureName=3 and that seems to have done the job.
From: vunder [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+5791131-840557044-305...@n2.nabble.com]
Sent: Wednesday, 1 December 2010
I had the same problem. First of all you must know, that installed features
has different state, even if they marked "Install from local source". You
need to add a new rule to condition, what will check state of the installed
freature. To check state of installig feature use & symbol, to check sta
Hmm, not my strong area but you might check to see that MigrateFeatureStates
is run before your check runs.
On Mon, Nov 29, 2010 at 8:20 PM, Loofsr wrote:
>
> G'day All,
>
> I am trying to display a MessageBox only if a feature has been selected and
> only if IIS 6 Compatability is NOT turned on
G'day All,
I am trying to display a MessageBox only if a feature has been selected and
only if IIS 6 Compatability is NOT turned on on a machine with IIS 7 enabled
(as the Feature needs IIS 6). This MesageBox should be displayed if the
conditions are met for it to be displayed when the Next butto
taller XML toolset.
Sent: Wed, October 6, 2010 12:28:23 PM
Subject: Re: [WiX-users] Feature: how to reinstall it or uninstall it alone?
You need to make the maintenancetype dialog send the changebutton to the
customize dialog in your version of wixui_installdir. Also, ARPNOMODIFY
should NOT be define
: little.forest [mailto:little.for...@ymail.com]
Sent: Wednesday, October 06, 2010 12:13 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Feature: how to reinstall it or uninstall it alone?
Hi,
We added a feature in our installer. The feature is a plugin for Outlook.
We defined a "Fe
Hi,
We added a feature in our installer. The feature is a plugin for Outlook.
We defined a "Feature" element in our Wix file. We also integrated
"CustomizeDlg" in our version of WixUI_InstallDir.wxs. Things work fine.
Here are two more requirements:
1. If the end user chooses NOT to install th
ate: Fri, 30 Jul 2010 15:41:35 -0500
From: "Joel Phelps"
Subject: [WiX-users] Feature Tree and Remove problem
To:
Message-ID:
<14550066402fb742af4a9f2226ded7658ac...@pleiades.sentinel1.com>
Content-Type: text/plain; charset="US-ASCII"
Ok,
I've seen a
helps [mailto:joel.phe...@ecollections.com]
Sent: Friday, July 30, 2010 1:42 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Feature Tree and Remove problem
Ok,
I've seen around the web this is a good place to ask questions about
WiX. I have been working on an install for one of my
Ok,
I've seen around the web this is a good place to ask questions about
WiX. I have been working on an install for one of my company's
products. I've run into a couple of issues that I have not been able to
figure out.
1. When selecting custom install, this brings up the feature tree with
all
s would be wise or even possible, depending on the packageing of
it and the legal issues.
-Original Message-
From: Boris Klyachko [mailto:bo...@qbf.com.au]
Sent: 27 July 2010 14:12
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Feature specific prerequisites
Hi there
Hi there
There have been a number of references in this mail list on how to include
prerequisites. The recommendation is to handle prerequisites in the
product's bootstrapper. However I have a slightly more complicated
requirement: A prerequisite (SQL Server Express) is required only if a
p
use this condition to execute your custom action
-Sanjay Rao
Boris Klyachko wrote:
> Hi there
>
>
>
> I need to perform some custom actions only if a particular feature of my
> product has been selected. If the product has been installed without that
> feature there is no need for Custom Actio
Hi there
I need to perform some custom actions only if a particular feature of my
product has been selected. If the product has been installed without that
feature there is no need for Custom Action. Can anyone please provide an
example of how to do it?
And there is more complex scenario:
On 6/7/2010 2:48 AM, Bijay Agarwal wrote:
>
>
The MSI doc says you should not set ADDLOCAL to all. Use AddLocal in
Publish elements instead. Then check a verbose log to see which features
are being installed.
--
sig://boB
http://joyofsetup.com/
--
I have to create a package with three features FeatureA, FeatureB & FeatureC.
The Feature selection is a RadioButtonGroup with selectable options being:
option 1 : FeatureA,FeatureB & FeatureC.
option 2 : FeatureB
option 3 : FeatureC
I have created a Custom Dialog:
Hi,
In my first msi there are four features. Based upon the selection of a
feature/features in the first msi, i have to copy files in my second msi.
How to catch the information of what feature(s) selected in the first msi?
Is there a way other than writing to a registry and read it from there
On 3/29/2010 3:15 AM, Rohit Sharma (SIDC) wrote:
> Remove control event does not HIDE the feature. It just puts a red-cross
> in front of the feature and provides user an option to enable it. (Refer
>
Yes, that's true. Like I said, you seem to be wanting features that the
selection tree contr
ssage-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Sunday, March 28, 2010 12:39 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Feature Tree modification based on property.
On 3/26/2010 12:10 AM, Rohit Sharma (SIDC) wrote:
> So is there no way I can do this, even if
On 3/26/2010 12:10 AM, Rohit Sharma (SIDC) wrote:
> So is there no way I can do this, even if I could HIDE the feature in
> selection tree that would work for me.
You can hide a feature by keeping its feature level at 0 or by using the
Remove control event.
--
sig://boB
http://joyofsetup.com/
===
Notice: This e-mail message, together with any attachments, contains
information of Symyx Technologies, Inc. or any of its affiliates or
subsidiaries that may be confidential, proprietary, copyrighted,
privileged and/or protected work product, and is meant solely for
the intended recipient.
't show the
> customsetup dialog to the user.
>
> -Original Message-
> From: Bob Arnson [mailto:b...@joyofsetup.com]
> Sent: Friday, March 26, 2010 6:31 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Feature Tree modification based on property.
. change the UI mode to INSTALLDIR and don't show the
customsetup dialog to the user.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Friday, March 26, 2010 6:31 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Feature Tree modification bas
On 3/25/2010 3:12 PM, Rohit Sharma (SIDC) wrote:
> I tried setting INSTALLLEVEL=101 from control event of next button as
> suggested in comment# 17 from Daniel in Bob's blog to trigger
> re-evaluation of feature condition but it didn't work for me.
>
I don't think it's documented to work. Feat
ix-users@lists.sourceforge.net'
Subject: Re: [WiX-users] Feature Tree modification based on property.
Hello Again,
Bob: I tried what is suggested in your blog but I am at the exact
situation which Peter faced mentioned in #9 on your blog.
So Bob as you mentioned there: "It's not poss
n I
HIDE the feature from selection tree.
Sam: I don't want user to modify to be able to modify the features once
I validate and set features they are entitled too.
Regards
Rohit
Message: 1
Date: Wed, 24 Mar 2010 13:02:59 -0500
From: Sam Domonkos
Subject: Re: [WiX-users] Feature Tree modif
On 3/24/2010 9:21 AM, Rohit Sharma (SIDC) wrote:
>
>
>
>
See http://www.joyofsetup.com/2007/05/30/feature-conditions-and-ui/.
Feature conditions aren't constantly evaluated; instead, they're
evaluated by specific actions, which sees the FEATUREx property not set
(or some o
I am still new to WiX, but maybe set each feature's level to 0 then
changing them to 1 with your custom action. Then when the user gets to
the customize dialogue they should be able to enable disable the feature.
--Sam
On 3/24/2010 8:21 AM, Rohit Sharma (SIDC) wrote:
> Hello
>
>
>
> I have a w
Hello
I have a wix project where I have 2 Main features and 1 Main feature has
two sub features. I have added a dialog box which I show to the user
which takes the productkey as input from the user. The return value from
my custom action lets me know whether the Feature 1 or Feature 2 are to
2009 3:53 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Feature selection and CustomAction commandline
Features have some action states and installed state. Using & or ! operator
can gain the state of the features in feature tree. eg. !FeatureName = 1.
aller XML toolset.'
抄送：
主题： Re: [WiX-users] Feature selection and CustomAction commandline
Try changing the first line to:
and tell us if it works.
-Original Message-
From: Arun Perregatturv [mailto:aperregatt...@napcosecurity.com]
Sent: Friday, November 20, 2009 10:49 AM
To: Gene
Try changing the first line to:
and tell us if it works.
-Original Message-
From: Arun Perregatturv [mailto:aperregatt...@napcosecurity.com]
Sent: Friday, November 20, 2009 10:49 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Feature selection and
#x27;General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Feature selection and CustomAction commandline
Well yes, does it work?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Blog: www.sebastianbrand.com
> -Orig
To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Feature selection and CustomAction commandline
>
> I tried as you said
> Value="1">INSTALLTYPE="CompleteServer"
> Value="2">I
age-
From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com]
Sent: Thursday, November 19, 2009 10:27 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Feature selection and CustomAction commandline
The INSTALLTYPE property will cont
xt="CardAccess Workstation" />
>
>
>
>
> This code works with selected feature it installs only those files but I need
> to know to in order to run CustomAction commandline.
>
> Maybe if I can check the value of INSTALLTYPE in CustomAction I can do
: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com]
Sent: Thursday, November 19, 2009 3:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Feature selection and CustomAction commandline
If you have a radio button group, we don't us
If you have a radio button group, we don't use the property you have associated
with the radiobutton group in the commandline.
How are you setting the InstallLevel using the radio buttons?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Crea
Hi,
I created a custom dialog for feature selection that has 3 radio button options
-
1. Server
2. Workstation
3. DB Server
I would like to know which of the feature the user has selected in order to run
a customaction with a commandline value.
Code looks something like this
Now,
Sheldon
发送时间： 2009-11-18 00:51:58
收件人： 'General discussion for Windows Installer XML toolset.'
抄送：
主题： [WiX-users] Feature Tree - Disable all Features
Hi,
I'm relatively new to WiX and am using WixUI_FeatureTree for the first time.
I have two small installations that I'm t
Hi,
I'm relatively new to WiX and am using WixUI_FeatureTree for the first time.
I have two small installations that I'm trying to combine into one script.
One for the Client and one for the Server. I'm trying to make both Features
in the FeatureTree to default to "Entire Feature will be Disabled"
Setting the REMOVE property on the final dialog was the missing piece of the
puzzle. In works when
following the method from your blog post. I thought the REMOVE property got
set internally.
Apparently not. Anyway, thanks for the help.
Rob
Rob Hamflett wrote:
> The approach in that blog po
otland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
>
> -----Original Message-
> From: Rob Hamflett [mailto:r...@snsys.com]
> Sent: 27 October 2009 15:26
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Feature not properly uninstalled when Lev
The approach in that blog post is essentially the same as what I tried with the
REMOVE condition.
I'm disabling the feature and using "AND NOT REMOVE" in the condition, whereas
the blog post talks
about enabling the feature with "OR REMOVE" in the condition. I tried the
latter approach, but i
Rob Hamflett wrote:
>
>
> I'm trying to work out how to get my product to uninstall after the user has
> removed Visual Studio.
>
http://www.joyofsetup.com/2008/05/16/make-sure-features-are-always-enabled-so-they-can-be-removed/
--
sig://boB
http://joyofsetup.com/
--
riginal Message-
From: Rob Hamflett [mailto:r...@snsys.com]
Sent: 27 October 2009 15:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Feature not properly uninstalled when Level 0
I've got a feature that I only want to be installed if Visual Studio
2005 C++ is installed. I search th
I've got a feature that I only want to be installed if Visual Studio 2005 C++
is installed. I
search the registry for a particular value to indicate if it is present or not,
and set this value
to a property called FOUND_VC80DIR, which initially has the value of "UNKNOWN".
On my feature I
ha
com]
Sent: Friday, October 02, 2009 4:31 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Feature 'ConfigureIISCompression' referenced in
column'InstallExecuteSequence'.'Condition' of row 'SetDoDynamicCompression'
is invalid.
HI,
I'm gett
HI,
I'm getting the bellow error while linking with light. Any idea?
error LGHT0204 : ICE79: Feature 'ConfigureIISCompression' referenced in
column'InstallExecuteSequence'.'Condition' of row 'SetDoDynamicCompression'
is invalid.
Following is the code ,
(&ConfigureIISCompression = 1)
Thanks,
1 - 100 of 190 matches
Mail list logo
