No. I have a custom action in my installshield installer that sets a registry
value before AppSearch. Then there are registrysearch actions in my wix merge
modules, which get executed during appsearch. There are two of these registry
searches; one works always because it is there before our
Are you saying that you have a custom action that sets a registry value and
then you use AppSearch to read the registry value in a custom action?
---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention?
Hello All,
I want my msi to run always with /l*v logfile command parameters from
setup.exe. I am generating setup.exe from Bootstrapper Manifest Generator.
setup.exe will pass the command line parameters to msi file.but I dont want to
send parameters to setup.exe to send to msi. I want msi to
Hello All,
I am using WixIIsExtension in my setup. As a result of this I notice that there
are 2 binaries which are getting added to MSI.
1) IIsSchedule
2) IIsExecute
If I extract these binaries from MSI and look at the dlls I see that these are
not signed.
I looked at the wix3 code
I know why this is happening now - not sure how to fix it.
The failed machines are multi-core, so the threads are running in parallel.
The custom action is being run in a separate thread so the key is not ready
before the merge module does its registrysearch.
The succeeding machines are single
A merge module is merged into your MSI and becomes part of it, so you'll never
find any evidence of VC runtime in Add/Remove Programs. If the VC++ files are
already installed then yours won't be, perhaps subject to file version
replacement rules, but if it's in the WinSxS folder you may see mult
I'm setting two properties using two different registry searches. One property
consistently sets as expected; the other does not.
I have confirmed in every install attempt that the registry key is indeed
there, set as expected.
With full logging passed into the msi, I see the following on the
I'm trying to customize the WixUI_Advanced dialog set, and had something
fairly simple, but it doesn't seem to work the way I expected. I'd like the
Welcome dialog to show up always (not just when doing a patch), so I copied
the WixUI_Advanced.wxs internals and changed the InstallSequence at the e
Hello.
First: the context: WiX v3.5, Windows 7 Enterprise
I'm intending to install the VC++ 9.0 redistributable from it's msm as
described in WiX's official documentation page [0]
Yet, even when my msi size augments in the same size as the msm and I can
see with Orca entrances related to the msm,
Currently I am having problems registering a WMI interface during a product
upgrade. Currently I am using a custom action to directly access the exported
functions in the file "InstallUtilLib.dll". Everything functions as expected
on a new install but when the product is upgraded but the wrong
I've been using Gmail and thought you might like to try it out. Here's an
invitation to create an account.
You're Invited to Gmail!
Alec Taylor has invited you to open a Gmail account.
Gmail is Google's free email service, built on the idea that email can be
intuitive, efficient, and fun. Gma
Universe implodes.
On Thu, Apr 28, 2011 at 3:07 AM, Blair wrote:
> I'm curious: what happens if you include but disable the cancel button?
>
> -Original Message-
> From: Tobias S [mailto:tobias.s1...@gmail.com]
> Sent: Wednesday, April 27, 2011 5:13 AM
> To: General discussion for Windows
I'm curious: what happens if you include but disable the cancel button?
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: Wednesday, April 27, 2011 5:13 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] old unanswered question rega
Hello.
I have several questions about detecting mechanism in Burn.
1) DetectPackageCompleteEventArgs contains "PackageId". Where could I
use this information? Could I somehow get access to .msi itself, described in
with detected "PackageId"?
2) DetectMsiFeatureEventArgs contains "P
hmmm ... just, by accident figured out something interesting. The [X]
seems to correspond with the [Cancel] Button. So when removing the
Cancel button the "Dialog Close / [X]" gets disabled. Unfortunately
this seems not be working for the ExitDialog.
2011/4/27 Tobias S :
> afaik not possible exce
Hi,I'm having some trouble getting a password protected PFX certificate to
install through WiX.
I'm using WiX 3.5.2519.0.
I include a PFX file as follows:
The value of $(var.ConfigSuffix) varies based on solution configuration (e.g. "
(Debug)", " (Stage)"). For "Release", it is set to an empty
Possibly 3 years too late to help Flavio...
...but for anyone else who has the same problem:
There is a slight improvement that can be made over putting your feature
specifications under the Product element.
Instead of using FeatureRef element to refer to feature specifications, what
can be done
afaik not possible except for modal dialogs. Assume here Tramontana
shows such one.
By default this is not a possible requirement for Windows Installer.
Regards,
Tobias
2011/4/27 william lee :
> Hi,
> I searched a lot online, but did not hit a result.
> The question is how the installer make th
I emailed difxt...@microsoft.com and received this response.
"AFAIK, Difx doesn’t do anything to explicitly support RemoveExistingProducts.
The scenario
described on that page would require it to rollback a partial install of a new
driver and the
previous uninstall of the old driver. The limi
Hi,
I am trying to register the wmi provider(basically a dll file) through
WIX Script.
Using GacUtil and Install.exe tools, I can able to register.
Many people suggested that GacUtil is not advisable..
Is there any other way to register the WMI Provider??
Thank You,
Preethi
On Mon, Apr 25, 2011 at 1:56 AM, Bob Arnson wrote:
> Deferred custom actions can only get a couple of system properties. To
> get any other properties (public or not), you need an immediate CA that
> writes CustomActionData for the deferred CA.
Funnily enough, this played straight into what I am
Hi,
I searched a lot online, but did not hit a result.
The question is how the installer make the decision to enable or disable the
dialog X(close) button on top right corner.
There is no dialog attribute to control it, but sometimes it just disabled,
for example:
http://www.tramontana.co.hu/wix/le
22 matches
Mail list logo
