I'm not the original person posing the question... but I did try that when I
wanted the functionality that Jeff is asking for. The problem I ran into
with the CloseApplication element is that it would either forcefully close
the application or schedule a reboot. It would not kindly prompt the user
This is something I implemented in my installer and I'm willing to share it
with the community. Basically I did it using a custom action. Here's the
relevant pieces from my .wxs file:
The RUNDEVENV variable allows me to control from the command line
I had a somewhat similar problem I had to deal with. Our product works with
both VS2008 and VS2010. I need to make my installer work with either or both
simultaneously. What I like doing in cases like this is to hide the feature all
together from the user when a feature is not compatible with th
I think what you're missing is the Product ID must also match, else Windows
Installer sees it as a completely different product, not just a different
version of the same product. Try putting the same GUID in your mailto:dave_mat...@ntm.org]
Sent: Thursday, January 28, 2010 7:49 AM
To: wix-users@
I am wondering if there is a way set a product dependency in the Windows
product install information somewhere. My goal here is that if the user tries
to uninstall product A (via our installer or via Add/Remove Programs) before
uninstalling product B (which has a dependency on A causing B to bre
simple CA you write) you could extend my "simple" approach:
-Original Message-
From: Cody Gibson [mailto:cgib...@artoftest.com]
Sent: Tuesday, January 26, 2010 7:04 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] PropertyRef Id="VS
commend a bootstrapper using the msbuild
GenerateBootstrapper task. I've got to go to a meeting now, but if you
have any questions about that approach feel free to ask and I'll pick up
later.
Ryan
-Original Message-
From: Cody Gibson [mailto:cgib...@artoftest.com]
Sent: 26 January 2010
ge.net
Subject: Re: [WiX-users] PropertyRef Id="VS90_ITEMTEMPLATES_DIR"
On 1/24/2010 1:18 PM, Cody Gibson wrote:
>
>
The AppSearch action doesn't guarantee an order the table's rows are
processed, so you can't rely on being able to use the results
Here's my problem:
We offer 2 products to our customers. Product A works standalone. Product B
relies on product A. Both products are owned by us (meaning we have total
control of the source code and the installers). I am responsible for the
installers. Currently both ship as .MSI's which are b
uary 24, 2010 8:14 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] PropertyRef Id="VS90_ITEMTEMPLATES_DIR"
On 1/24/2010 1:18 PM, Cody Gibson wrote:
> Depth="1" AssignToProperty="yes">
>
The AppSearch action doesn't guarantee an order
t: Re: [WiX-users] PropertyRef Id="VS90_ITEMTEMPLATES_DIR"
You need to make sure you have a reference to the VS90_ITEMTEMPLATES_DIR.
Unfortunately, the usage of the property (aka: using []) will not create a
reference. In this case, just add a
On Sun, Jan 24, 2010 at 10:18 AM, Cody Gibson
0:18 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] PropertyRef Id="VS90_ITEMTEMPLATES_DIR"
On 1/17/2010 8:39 PM, Cody Gibson wrote:
> Why does this wxs file work (i.e. the single file to install is installed at
> the correct location)
>
Usually, people ask why
Why does this wxs file work (i.e. the single file to install is installed at
the correct location)
http://schemas.microsoft.com/wix/2006/wi";>
but not this one?
http://schemas.microsoft.com/wix/2006/wi";>
uot;..\..\..\..\..\..\..\..\..\Program Files\Windows Installer XML
v3.5\bin\WixUIExtension.dll" -ext "..\..\..\..\..\..\..\..\..\Program
Files\Windows Installer XML v3.5\bin\WixVSExtension.dll" Product.wxs
obj\Release\_ClassLibrary1.wxs
candle.exe(0,0): error CNDL0103: The syst
I am in the midst of upgrading our product to be VS 2010 compatible. We're
using WIX to generate a .msi installer. I've upgraded to WIX 3.5.1309.0 and
have run into a snag.
Specifically I'm having a problem with the HEAT tool in this version. It is
having trouble working with our VS2010 convert
15 matches
Mail list logo
