Thanks Pavan, Phil.
Turned out I had defined my custom action incorrectly:
CustomAction Id=CopyLogFile Property=MsiLogFileLocation
ExeCommand=xcopy.exe /h /r /y quot;[MsiLogFileLocation]quot; c:\logs\
Impersonate=yes Return=ignore /
Since this is a type 50 CA, Property should be set to
FYI, I had to this issue today and copying the ProjectAggregator2.msi
next to my wix3.7.exe worked. (I have both VS 2005 and 2008)
Log entries for failure:
[105C:11BC][2014-03-28T15:42:31]i000: Caching bundle from:
Yes.
If the AssemblyVersion is what you're after, Microsoft MSBuild supports you
directly:
!-- Get the version info from the assembly to use as the version number of the
assembly --
Target Name=ExtractVersionInfo
GetAssemblyIdentity
Sorry for the delay, Mike. I had moved on to my next hurdle of how to
write/customize my own BA/UI.
I am using the default feature as shown below (nothing conditional):
Feature Id='All' Title='All Components' Description='Installs all
components' Level='1'
ComponentGroupRef Id=CR1 /
With an MSI one can open it and run a query on it to find its UpgradeCode and
ProductCode. Bundles have an UpgradeCode; however, is there an easy way to get
that from the EXE itself once built? I'm wanting to update our IsInstalled tool
to support them, and to ensure that one is dealing with
Hi,
We use MSI Major Upgrade to update our products on servers. In
the light of some recent failures during upgrade, we have been working towards
hardening our installation package so that a reboot can be scheduled in the
worst case. I have been looking at various Installer properties/actions
Unfortunately I don't understand much of that preamble. If you're
getting failures during upgrades, perhaps explain how reboots are
involved, if that's what you're looking at. I've only heard the term
hardening in the sense of making a system more resistant to cyber
attack (look it up!) so maybe
Thank you the detailed
explanation, I really appreciate it.
One issue that we
encountered during an upgrade was that a process was holding onto an exclusive
handle to one of the files being replaced during upgrade. This process ignores
Ctrl+C controls and is managed by a parent process which
Please help me understand service dependencies and service Groups.
Scenarios:
Service B (WcfServiceHost) depends on Service A (LogService). Service A fails
which stops Service B. The recovery restarts service A, will it restart
Service B? Also, if service A fails which stops service B,
Out of curiosity, which process hols your file handle? As Phil said,
if it's a badly written service etc, it would be better to fix the
broken process than to force the installer to perform actions that
aren't needed in order to hide faulty programming. It's been my
experience that the
I would like to disable and show default value for the ComboBox if it is
MajorUpgrade. otherwise enable ComboBox and no item should be selected just
show the list when dropdown is selected.
Property Id=DefaultValueID Value=test/
Control Id=ComboBox1 Type=ComboBox X=130 Y=85 Width=130
Height=17
Try:
ComboBox Property=ITEMNAME
ListItem Text= Value=1/
ListItem Text=One Value=2/
ListItem Text=Two Value=3/
/ComboBox
Quoting geshete getyetesf...@yahoo.com:
I would like to disable and show default value for the ComboBox if it is
MajorUpgrade. otherwise
This is an external process and we do not have any control over it. we are in
talks with the process owners to see why it opens a handle in exclusive mode
but I would like to know if there is something that we can do to avoid upgrade
failures in such cases (such as scheduling file copying after
I got this error message:
The ListItem/@Text attribute's value cannot be an empty string. If a value
is not required, simply remove the entire attribute
--
View this message in context:
Would this work? You do know the process name correct?
http://wixtoolset.org/documentation/manual/v3/xsd/util/closeapplication.html
Carter
Quoting Suryadeep Biswal surya6...@hotmail.com:
This is an external process and we do not have any control over it.
we are in talks with the process
Add the condition for enable also and try:
Condition Action=enable NOT WIX_UPGRADE_DETECTED /Condition
-Original Message-
From: geshete [mailto:getyetesf...@yahoo.com]
Sent: Friday, March 28, 2014 2:03 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WIX ComboBox default
Try List Item Value =1, ie leave off the text attribute. If it still
complains try ListItem w/ nothing and as a last resort write None
Selected as the text property.
Carter
Quoting geshete getyetesf...@yahoo.com:
I got this error message:
The ListItem/@Text attribute's value cannot be an
Thank you for your replay.
I used WIX_UPGRADE_DETECTED property to disable the combox for MajorUpgrade.
That works fine. But how can I assign the Property of ComboBox to
DefaultValueID instead of ITEMNAME for MajorUpgrade.
it should be something like this.
if (WIX_UPGRADE_DETECTED)
Control
I could give this a try, but is it not the same as the Installer invoking
Restart Manager to terminate the processes that hold a handle to the files
being replaced? The problem is not the process termination, it is actually the
process restarting before the file copy action. we can keep
What is the UI dialog that comes before the Dialog that contains this ComboBox?
-Original Message-
From: geshete [mailto:getyetesf...@yahoo.com]
Sent: Friday, March 28, 2014 2:43 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WIX ComboBox default value
Thank you for
Another dialog for user credentials. If the user credentials is validated, it
opens the dialog that contains the comboBox.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-ComboBox-default-value-tp7593832p7593842.html
Sent from the wix-users
Kill the parent and you'll have no more issues with the children. smile/
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Suryadeep Biswal
Hi Mike,
I got the installation to work using the Node=document method. The xml
content is now correctly written during install mode.
To remove the xml content during uninstall, I need to specify each node in a
sequence (working from the child elements to outer elements), correct? I cannot
use
Try publishing the Property in the Control for Next on the User Credentials UI
dialog. Something like this:
Control Id=Next Type=PushButton X=248 Y=243 Width=56 Height=17
Default=yes Text=!(loc.WixUINext)
Publish Property= ITEMNAME Value = ITEMNAME
Order=0WIX_UPGRADE_DETECTED/Publish
24 matches
Mail list logo
