sequence:
Custom Action=SetProperty1 Before= UpdateKey
Custom Action= UpdateKey After=PublishProduct
--Pavan
-Original Message-
From: Nan Zang [mailto:naz...@microsoft.com]
Sent: Wednesday, March 05, 2014 9:58 PM
To: General discussion about the WiX toolset.
Subject: Re
Hi,
I am trying to read a regkey value in the msi. But, this regkey has special
ACL set on it, which only allows Local System/Administrator to read it.
I am using RegistrySearch Element to read the regkey. The operation will work
if the msi is launched through elevated cmd window. But, if
-
From: Nan Zang [mailto:naz...@microsoft.com]
Sent: Wednesday, March 5, 2014 1:33 PM
To: General discussion for Windows Installer XML toolset.
(wix-users@lists.sourceforge.net)
Subject: [WiX-users] read a regkey with special permission
Hi,
I am trying to read a regkey value in the msi
I tried it, however it doesn't work fully for my case. Besides the OS version,
I also need to check the architecture of the OS. I want to block 64 bit package
to be installed on a 32 bit OS. If I set the condition, the installation will
be blocked, however, I didn't see I can customize the
I would like to try the option of change the prereq-BA to a different native BA
which do the precheck. I don't have much knowledge about how BA. Do I need to
modify wix source code to achieve this? Could you give me some more details on
how to do it?
1. Which interface my prereq BA needs to
Hi,
I met with the same problem with the MBA precheck. Definitely, I can have the
code in my MBA to check the pre conditions, however, I think the following
scenario is totally broken. Eg. We want to block installation of our product
on the OS vista or before.
A user uses a vista machine
Hi,
I am building a bootstrapper based on the managed BA (I am using a customized
WPF UI), but met with the following issue.
My BA.exe refers to an MsiPackage, which contains two features (WebService and
AdminTool).
If everything is not installed, if user selects AdminTool, the BA will call
try to control feature states using the properties. Instead, turn on
EnableFeatureSelection and handle the PlanFeature callback from the engine.
The ADDLOCAL property and friends won't give you the control necessary to
succeed.
On Mon, Apr 1, 2013 at 2:10 PM, Nan Zang naz...@microsoft.com wrote
My MSI has two dummy feature as listed below.
Feature Id=FULLPRODUCTION Title=RMSSetupInstaller
ComponentGroupRef Id=ProductComponents /
/Feature
Feature Id=ADMINCONFIGURATIONTOOL Title=RMSAdminInstaller
ComponentGroupRef Id=AdminComponents /
I think I found the issue.
In bundle msipackage definition I need to define the following. Property to
make it work
msiproperty name=ADDLOCAL value=[ADDLOCAL]/
Sent from my Windows Phone
From: Nan Zangmailto:naz...@microsoft.com
Sent: 2/13/2013 7:15 PM
To:
Hi,
I am working on a setup program which needs to meet the following requirements.
I tried to use bootstrapper to accomplish those, but, didn't figure out a way
to do so. Thank you in advance for any help or hint.
1. Is that possible to install a dependency automatically which will
you need to assign.
Jacob
-Original Message-
From: Nan Zang [mailto:naz...@microsoft.com]
Sent: Tuesday, February 12, 2013 5:10 PM
To: General discussion for Windows Installer XML toolset.
(wix-users@lists.sourceforge.net)
Subject: [WiX-users] questions on bootstrapper
Hi,
I am working
:1700][2013-02-12T23:07:49]: Detect complete, result: 0x0
From: Nan Zang
Sent: Tuesday, February 12, 2013 8:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] questions on bootstrapper
Jocob,
Thank you for your
My problem is solved.
I found I used a wrong cultureid (jp-jp) but not ja-jp, also with adding the
codepage=932 definition in wixlocalization, it built correctly.
Thanks for your time,
Nan
From: Nan Zang
Sent: Thursday, January 05, 2012 5:40 PM
To: General discussion for Windows Installer XML
HI,
I have a simple msi only use wixui_installdir dialog set. I need to build a
Japanese version of the msi.
When I specify the -cultures JP-JP parameter when running light.exe, I got
hundreds of error complaining $(Loc.X) is not defined. Where can I find the
Japanese strings for the
Hi All,
I tried using ExitDialog (WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT) to allow the
user to control whether our application is run at the end of the install.
However, the entire checkbox control has a gray background. Is it possible to
change the background color to white or make it
Hi,
I found the answers to the launching application thread are really helpful.
And I did my msi following those instructions.
However, I still got a question:
I got an msi file, and an application which requires administrator privilege
to launch.
1. If I run the msi through the cmd
Hi,
I am not sure if this is a wix question. But I prefer to get some advise from
the setup expert here.
I want to make an msi to install files (application.exe and
application.exe.config) into Program Files Folder, and then from msi to launch
another application to modify the
I am going to write a registry key value which is supposed to be
c:\program files\my product\eventmessages.dll. My target dir is c:\program
files\my product.
However, when I use the following statement in the wix:
Registry Id=EventMessageFile
Name=EventMessageFile
Hi All,
I am new to wix, and got stuck to get my first wix project run. I need some
help.
Here is my problem:
I have a Windows server 2008 x64 machine and I used wix 3.0.5006.0 x64
binaries.
When I build my wix project, I got the following error:
light.exe : error LGHT0216 : An
/
/Component
/DirectoryRef
!-- Step 3: Tell WiX to install the files --
Feature Id=MainApplication Title=Main Application Level=1
ComponentRef Id=MyApplication.exe /
/Feature
/Product
/Wix
From: Nan Zang
Sent: Wednesday, February 18, 2009 2:44 PM
To: 'wix-users
21 matches
Mail list logo