In the InstallExecuteSequence is it possible for Action-B's condition to
reference the enable/disable state of another action, Action-B?
--
Tony
--
Comprehensive Server Monitoring with Site24x7.
Monitor
Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: 23 July 2010 13:18
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] InstallExecuteSequence completely ignored
Dear Pally,
Am 23.07
Dear Pally,
Am 23.07.2010 11:04, schrieb Pally Sandher:
> MSI (c) (74:80) [21:07:26:477]: Doing action: ValidateProductID Aktion
> 21:07:26: ValidateProductID.
>
> That's the InstallUISequence not the InstallExecuteSequence.
Indeed! I changed now to InstallUISequence and now it works!
But why?
E in the
> MSI (use ORCA to see what got into the MSI)?
>
> -Original Message-
> From: Lukas Haase [mailto:lukasha...@gmx.at]
> Sent: Thursday, July 22, 2010 12:12 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] InstallExecuteSequence completely ignored
&
Dear Rob,
This was also my first guess. But I deleted and recompiled a few times.
I even renamed the file.
I do not know which entry in the logfile you mean but the one line
containing "cache" on the top is:
MSI (c) (04:E8) [13:50:57:178]: Resetting cached policy values
Another two lines attr
t: 23 July 2010 07:40
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] InstallExecuteSequence completely ignored
Is your added authoring in a fragment that has other things that ARE in the MSI
(use ORCA to see what got into the MSI)?
-Original Message-
Is your added authoring in a fragment that has other things that ARE in the
MSI (use ORCA to see what got into the MSI)?
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: Thursday, July 22, 2010 12:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users
Hmm, my first guess is that the new MSI isn't actually being used for the
install. Is it possible the MSI is already cached and you're re-running
using the cached MSI? The verbose log file will show you at the top.
On Thu, Jul 22, 2010 at 12:12 PM, Lukas Haase wrote:
> Hi,
>
> As proposed in on
Hi,
As proposed in one mail I wrote a DLL for detecting old installations.
But WiX seems to completely ignore InstallExecuteSequence!
I played around, tried different things but it is just ignored!
For testing I just added this to my file:
Notepad.exe
Even if I install with msiexec /i
even hard-to-solve problems in the list. If you need more hand-holding,
there are several people willing to provide more extensive help for a fee.
-Original Message-
From: Joshua Chambers [mailto:jos...@tdronline.com]
Sent: Tuesday, June 01, 2010 3:32 PM
To: wix-users@lists.sourcefor
See... what is wrong here? I included a "reference" to the
backupSettingsAction project in the WiX project.
--
View this message in context:
http://windows-installer-
"The path of the CommonAppData directory is found in the "CommonAppData"
property after CostFinalize. The same with all the entries in the Directory
table."
Okay, those are properties in the WiX file, no? How can I pass that to my
C# program (custom action) to manipulate the file? I'm confuse
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] InstallExecuteSequence problem!
I am now working on getting the custom action going to back up the existing
settings.xml file. I am using this page as a guide:
http://blogs.msdn.com/b/jasongin/archive/2008/05/23/custom-action-project-te
mplates.as
I am now working on getting the custom action going to back up the existing
settings.xml file. I am using this page as a guide:
http://blogs.msdn.com/b/jasongin/archive/2008/05/23/custom-action-project-templates.aspx
I have created a custom action project, and it builds. I am a bit confused
th
AH... okay, your response now finally makes some sense. Custom action is
what I was just looking at, as I don't have much of a notion of the
patching...
Just for the record, I DID NOT author the original installer for this
application, I am simply coming in after the fact with a new version.
online.com]
Sent: 01 June 2010 19:16
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] InstallExecuteSequence problem!
I have already tried this! I have been through several rounds of it,
and the problem is that if RemoveExistingProducts is set after
InstallFinalize (which makes t
I have already tried this! I have been through several rounds of it, and the
problem is that if RemoveExistingProducts is set after InstallFinalize
(which makes the Settings.xml file remain intact), the CompanionFile does
work to show that the file is replaced, however, the Pathways.MDF file then
ing, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Joshua Chambers [mailto:jos...@tdronline.com]
Sent: 01 June 2010 17:24
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] InstallExecuteSequence problem!
Okay! I have finally more closely i
Okay! I have finally more closely identified the problem I'm having. In my
installer, I was attempting to get a settings file to REMAIN INTACT on a
major upgrade. I finally got this to work with the suggestion to set
This is successful in forcing this component to leave the origina
Oh, thanks!
I was not know about "uppercase=public" rule for msi properties.
I have changed properties' names, used in custom action to uppercase and it
works right.
--
Download Intel® Parallel Studio Eval
Try the new sof
Are your properties public, meaning are their Ids uppercase? If they're not,
they won't pass from the UI to the Execute phase.
example:
And do you see the property being set in the install log? Like...
MSI (c) (98:F0) [12:04:32:046]: PROPERTY CHANGE: Adding CHECKBOX_PROPERTY
property. Its va
Hi!
First, sorry for my bad english (may be..).
I have custom dialog with checkboxes, binded to properties and some actions
attached to controls in this dialog. This works well. But then I need to use
values of this properties in custom action, executed in
InstallExecuteSequence and.. this proper
In article
<5e7723298293ea4b8c5fac913740a9cc212b5...@tk5ex14mbxw652.wingroup.windeploy.ntdev.microsoft.com>,
Dan Giambalvo writes:
> During our InstallExecuteSequence we decrement an install count for
> the user via a Custom Action.
What does the "install count" mean?
There may be a way
ers@lists.sourceforge.net
Subject: [WiX-users] InstallExecuteSequence modifying Dialogs
During our InstallExecuteSequence we decrement an install count for the user
via a Custom Action. After that takes place, we want to change the
messaging of our Windows Installer UI (Cancel dialog, UserExit dialog,
During our InstallExecuteSequence we decrement an install count for the user
via a Custom Action. After that takes place, we want to change the messaging
of our Windows Installer UI (Cancel dialog, UserExit dialog, etc) to alert the
user to this fact (as it is non-reversable.) I'm having troub
: 11 August 2009 21:51
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] InstallExecuteSequence and merge modules
IMHO, if a merge module requires certain actions it should include them
itself (it has that capability). Alternately, the author of the me
re minimal approach (which leads to faster/leaner install
packages).
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Tuesday, August 11, 2009 6:55 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] InstallExecuteSequence and merge modul
I have third party merge module and I found that I need to add elements
to the to get it to install properly e.g.:
I did this by
well, this is just a matter of
taste.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Wednesday, January 21, 2009 9:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] InstallExecuteSequence in a fragment?
Eitan Behar wrote:
>
taller XML toolset.
Subject: Re: [WiX-users] InstallExecuteSequence in a fragment?
Eitan Behar wrote:
> What I did was to include an empty ComponentGroup in the fragment, and a
> reference to the component group from Product.wxs, this way I don't need to
> set a CustomActionRef
Eitan Behar wrote:
> What I did was to include an empty ComponentGroup in the fragment, and a
> reference to the component group from Product.wxs, this way I don't need to
> set a CustomActionRef for every custom action.
>
You don't need a CustomActionRef for every custom action, just one for
ustom action.
Kind of:
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Wednesday, January 21, 2009 6:42 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-
r Windows Installer XML toolset.
> Subject: Re: [WiX-users] InstallExecuteSequence in a fragment?
>
> Jeremy Lew wrote:
> > Problem is, the InstallSequence seems to be ignored. I'm guessing
> that
> > this is because it's not referenced in the Produ
toolset.
Subject: Re: [WiX-users] InstallExecuteSequence in a fragment?
Jeremy Lew wrote:
> Problem is, the InstallSequence seems to be ignored. I'm guessing
that
> this is because it's not referenced in the Product element, which
lives
> in a different file. How can cause InstallS
Jeremy Lew wrote:
> Problem is, the InstallSequence seems to be ignored. I'm guessing that
> this is because it's not referenced in the Product element, which lives
> in a different file. How can cause InstallSequences defined in
> fragments to be merged into the one in the Product? Is the only
Hey Jeremy,
In order to include code inside a fragment you must reference something.
>From the below snippet you provided you could reference a single
CustomAction using
http://wix.sourceforge.net/manual-wix3/wix_xsd_customactionref.htm>/>.
This will link in the rest of the fragment.
Thanks,
Bri
Trying to be tidy, I pulled out the CustomAction declarations relating
to a particular aspect of my install into its own .wxs file.
I have
[...sequence the custom actions declared above]
Problem is, the InstallSequence seems to be ign
Doh! I figured out that the reference to the File ID was wrong, so the
path to the assembly was evaluating to a blank string. Turns out
standard action sequence works fine for this scenario.
Thanks,
Chris
Alexander Shevchuk wrote:
> Hi Chris,
>
> Sorry, I am still on WiX 2, but that should n
PROTECTED] On Behalf Of Chris Eldredge
Sent: Thursday, January 31, 2008 1:15 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] InstallExecuteSequence for Sql Actions
I'm trying to create an MSI that installs a .NET assembly and registers
it for use in SQL Server 2005.
The problem is
Actually, I'm trying to load the assembly from the file system, not the
GAC. Does that change your answer?
Thanks,
Chris
Adam Majer wrote:
>
> No. GAC is updated after MSI install is finalized. Wix has no control
> over this.
>
> - Adam
>
>
---
Chris Eldredge wrote:
> I'm trying to create an MSI that installs a .NET assembly and registers
> it for use in SQL Server 2005.
>
> The problem is that the SQL I'm executing inside a SqlString is telling
> SQL Server to load the assembly, but when I install the MSI it seems
> that the assembly
I'm trying to create an MSI that installs a .NET assembly and registers
it for use in SQL Server 2005.
The problem is that the SQL I'm executing inside a SqlString is telling
SQL Server to load the assembly, but when I install the MSI it seems
that the assembly hasn't been copied to its final d
e.net
Subject: [WiX-users] InstallExecuteSequence: checking mode
I have an InstallExecuteSequence block, within which I currently run
actions depending on whether the installation is installing or removing.
I'd like to extend the installing condition to include the Change/Repair
modes that are av
Craig Ward wrote:
> I have an InstallExecuteSequence block, within which I currently run
> actions depending on whether the installation is installing or removing.
> I'd like to extend the installing condition to include the Change/Repair
> modes that are available in the maintenance dialog.
>
I have an InstallExecuteSequence block, within which I currently run
actions depending on whether the installation is installing or removing.
I'd like to extend the installing condition to include the Change/Repair
modes that are available in the maintenance dialog.
I'm trying this but with no suc
am modifying the existing msi using orca.
unfortunately I dont have any wxs files or the environment to generate msi.
Bala.
Message: 4
Date: Thu, 5 Jul 2007 04:11:31 -0700 (PDT)
From: fiordean dacian
Subject: Re: [WiX-users] InstallExecuteSequence
To: "Balakrishna.BK" ,
wix-u
using orca.
unfortunately I dont have any wxs files or the environment to generate msi.
Bala.
Message: 4
Date: Thu, 5 Jul 2007 04:11:31 -0700 (PDT)
From: fiordean dacian
Subject: Re: [WiX-users] InstallExecuteSequence
To: "Balakrishna.BK" ,
wix-users@lists.sourceforge.net
To: wix-users@lists.sourceforge.net
Sent: Thursday, July 5, 2007 1:05:28 PM
Subject: [WiX-users] InstallExecuteSequence
Hi,
I am newbie to msi technology and I have the following question in
InstallExecutesequence.
I am editing my existing msi file using orca and want to swap sequenc
Hi,
I am newbie to msi technology and I have the following question in
InstallExecutesequence.
I am editing my existing msi file using orca and want to swap sequence
numbers of appsearch and launchcondion
actual
Appsearch = 400 as sequence number and
Launchcondition = 1
49 matches
Mail list logo
