One thing I would check is the build configuration.
Is the pre-processor variable defined for both Debug and Release
builds?
Maybe it's only defined for Debug build of the Wix setup project but
your build server is building the Release config.
-Original Message-
From: Bair, Steve [mai
Have you tried setting the Impersonate attribute to "no" in your CustomAction
element?
http://wix.sourceforge.net/manual-wix2/wix_xsd_customaction.htm
-Original Message-
From: Rahul Ramesh Ekbote [mailto:rahu...@microsoft.com]
Sent: Tuesday, 3 May 2011 12:06 a.m.
To: chr...@deploymente
n\v3.5\ENU
So your launch condition would look something like:
Cheers,
Sharad Patel
Winscribe NZ
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Tuesday, 8 March 2011 11:42 a.m.
To: General discussion f
Cheers
Sharad Patel
Winscribe NZ
-Original Message-
From: Brown, Glenn [mailto:glenn.br...@savogroup.com]
Sent: Wednesday, 16 February 2011 9:08 a.m.
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Newbie Visual Studio Question
Hi Folks,
I'm just starting to get the ball
We had a similar requirement. This is what we ended up using...
---
http://schemas.microsoft.com/wix/2006/wi"; >
---
Cheers
Sharad Patel
Winscribe NZ
-Original Message-
From: Deepika Gakhar [mailto:deepi...@microsoft.com]
Sent: Wedne
e='DatabaseServer']/value"
Cheers
Sharad Patel
-Original Message-
From: Gregg Swanson [mailto:gregg.swan...@microsoft.com]
Sent: Tuesday, 8 February 2011 10:10 a.m.
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Assistance using XmlConfig (assuming that is
thecorr
> 1. Why is this being written to HKCU on server instead of HKLM?
> 2. Any idea where it picked up the
"Software\Classes\VirtualStore\Machine\Software" path?
It's File and registry virtualization in Windows.
http://support.microsoft.com/kb/927387
> 3. How do I force it to write to the HKLM path,
If you are using VSTO then these two Office add-in articles on MSDN will
help you.
1. Registry Entries for Application-Level Add-Ins
http://msdn.microsoft.com/en-us/library/bb386106.aspx
2. Deploy add-ins that use VSTO3:
http://msdn.microsoft.com/en-us/library/cc563937.aspx
The second article
the issue sometimes before and the only solution was a
InstallScript InstallScript CA for handling that. (Was an
InstallShield solution and not a WiX project)
2010/12/8 Sharad Patel :
> Hi Igor. Thanks for that. After reading your and Pally's message I
> realized that the project had &q
blem for us to write a managed
custom action based to .NET 4.0.
Cheers
Sharad Patel
-Original Message-
From: Igor Paniushkin [mailto:ipaniush...@sdl.com]
Sent: Wednesday, 8 December 2010 11:05 p.m.
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Can
ly. Of course without
the RegistrySearch condition the installer works just fine on x64
systems but we would like to be able to detect AppFabric.
So far writing an unmanaged (or managed) custom action seems like our
only option.
Is there a way to achieve this without a custom acti
mmented out the 'WixUICostingPopupOptOut' property and
the error has gone away but I'm not sure if the "Please wait..." bug is
going to come back now.
Does anyone know if there is an alternate way to opt-out of the costing
dialog that works in the escrow release? Or is that p
12 matches
Mail list logo
