On 02/02/2012 01:15, Rajesh Khetan wrote:
Thanks Phil. Is there a way to ensure in WXS file, such that the service gets
started after all the dependent dlls are installed?
You could add a commit custom action to start the service. This will
run once the install has been finalised, so the
Hi Blair,
Thank you very much for this new insight.
The use of WixLib sounds good; the actual wxs files of product A are
already in a WixLib, so that they can be shared between the installer
and MSM. The only thing is that the repository of product B then has to
have access to the repository of
Hi,
Good to know about Dark.exe, didn't notice it till now :)
I'm having problems after converting my Original MSI to WXS file, I try
to Candle it so I can then light it to get the wixpdb, but I get this
error:
\\sqlsrv\tsinstallers\TestShell Suite\4.6.255 SP1\Data\Driver
Builder\TestShell
One more thing I found out: (concerning the msi to wixpdb using dark,
candle, light)
I have another tag in my setup.wxs:
?if $(var.HasQsConfig) = true ?
CustomAction Id=RunConfigInstall FileKey=QsConfig.exe
ExeCommand= Execute=immediate Return=ignore /
CustomAction
Hi,
We are having a installer having 2 features(each feature is install a
windows service which do some jobs).
Both services/features can be installed on multiple computers and then
using application's user interface user can interconnect all the
application components. Thereafter all
The location of the exes is taken from the registry and put in $(WixToolPath).
Can you check the InstallRoot value under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Installer XML\3.5
or
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Installer XML\3.5
and see if it is correct?
Is there some way to log the value of the Burn Built-in Variables. At the
moment the log just tells me that my test resolved to False and I can't
tell if the value of Privileged is set to False or is undefined. I've tried
testing against some of the other built-in variables and had unexpected
Can somebody provide with the table that can show which conditions to use for
Custom Actions to run only on Install only, Install and Modify, Modify
only and Uninstall only?
Thanks in advance.
--
View this message in context:
Certainly. I'll get right on it.
--
John M. Cooper
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, February 01, 2012 6:16 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WriteIIS7ConfigChanges: Error
Bug is 3483215.
--
John M. Cooper
-Original Message-
From: John Cooper
Sent: Thursday, February 02, 2012 8:02 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WriteIIS7ConfigChanges: Error 0x80070057: Failed get
handlers section for DirProp
I'm having a problem with getting an EventSource to work correctly on XP,
the same install
works fine on Win7.
Component Id=ApplicationExe Guid=*
File Id=mergefarms.exe
Source=$(var.MergeFarms.TargetDir)$(var.MergeFarms.TargetFileName) /
util:EventSource Log=SnapPlus
Hi!
I'm pretty new to the toolset so bear with me :)
I'm using 3.5, and am trying to harvest the dll's from the c# project, using
the property Harvest set to true in Visual Studio.
I do get a ComponentGroup named x.Binaries, but it don't contain any of the
dll's that my project is
If you were using the MSM simply because it is a container of files
themselves, you can get the same effect by binding the files to the WixLib
by supplying the -bf flag to lit.exe. In MSBuild/VisualStudio, you can do
this by setting either of the following properties to true in the WixProj
file:
Unfortunately heat doesn't harvest referenced assemblies in a project.
Neil
-Original Message-
From: Terje Sandstrom [mailto:te...@hermit.onmicrosoft.com]
Sent: 02 February 2012 19:02
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Harvesting dll's referenced in a c# project in
I suspect that the MSM would also fail validation. If it fails, can you get
your third party to fix their MSM until it passes validation?
Blair
-Original Message-
From: Sireesha Jakku [mailto:sireesha_ja...@persistent.co.in]
Sent: Thursday, February 02, 2012 3:14 AM
To:
This is the registry key used to populate the
NETFRAMEWORK40CLIENTINSTALLROOTDIR property. Can you verify that the
registry key is set propertly on the XP box?
HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Client
InstallPath
Also in your verbose installation log you should see the
What did dark write in line 2939 of TestShell DriverBuilder Setup.wxs?
-Original Message-
From: tome...@qualisystems.com [mailto:tome...@qualisystems.com]
Sent: Thursday, February 02, 2012 1:19 AM
To: wix-users@lists.sourceforge.net
Cc: alex...@qualisystems.com; rone...@qualisystems.com
I'm assuming that the attribute-less InstallExecute in this email is the
line in the error message, correct? If so, then this really looks like a bug
in dark.exe.
The ?if? from the original source shouldn't have anything to do with the
this bug in dark.exe.
Go ahead and fix that line in the
Thanks !
Surprising, but.
What is the workaround ?There is a workaround, right ?
Best regards
Terje
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 2. februar 2012 21:24
To: General discussion for Windows Installer XML toolset.
Subject: Re:
FWIW, I'm a strong advocate of the use of internally generated merge
modules to support decentralized setup development, but I am very, very
wary of using merge modules from third parties. It usually doesn't end
well.
From: Blair os...@live.com
Sent:
On Thu, Feb 2, 2012 at 2:54 PM, Blair os...@live.com wrote:
This is the registry key used to populate the
NETFRAMEWORK40CLIENTINSTALLROOTDIR property. Can you verify that the
registry key is set propertly on the XP box?
HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Client
I am new to WiX Votive but not new to installers or setups by any means.
Briefly, I am getting spun up on WiX as a plausible upgrade from the basic
Setup (VDPROJ) project that Visual Studio 2010 offices out of the box.
Can someone tell me briefly, how does it compare? Besides doing what the
Yes. But I don't want to include these files. I would like to see simple
chart which use these properties e.g. REMOVE=ALL, Installed, NOT
Upgrading, NOT Uninstalling AND NOT UPGRADINGPRODUCTCODE and tell me where
they are applicable. But I think I'll try to get that information from this
link that
Not today but it's been asked before.
On Thu, Feb 2, 2012 at 3:15 AM, Boyd Ludlow boyd.lud...@gmail.com wrote:
Is there some way to log the value of the Burn Built-in Variables. At the
moment the log just tells me that my test resolved to False and I can't
tell if the value of Privileged is
Doesn't compare really at all. VDPROJ is all Designer based.
pointy-clicky type stuff. :)
WiX toolset is source code based, typey-typey type stuff.
You can create custom dialogs (by typing in source code) but there isn't a
drag and drop editor in Votive today. Some people said WixEdit did
Can you provide more context. Are you sure the condition is getting
included in the Bundle?
On Thu, Feb 2, 2012 at 3:08 PM, David L. Beckwith
beckw...@interaccess.comwrote:
I'm trying to prevent a burn application from installing on Windows 8 but
without success. I've tried to set the
Better to write your CustomActions to be data driven and use Component
states to control when things get installed. That's what the WiX custom
actions do so there is plenty of example code.
On Thu, Feb 2, 2012 at 8:05 PM, Amit Khurana amit.khur...@gmail.com wrote:
Yes. But I don't want to
27 matches
Mail list logo
