Martin,
Package ID should always be different. That's why it is set to '*'. For major
upgrade to work, you need to change product id and version (version in MSI is
first 3 fields. If two versions have the same first 3 fields and differ only
in the fourth field, as far as MSI concerned -
Try to set SelectionLanguage attribute to XPath.
From the doc on XmlFile:
Specify whether the DOM object should use XPath language or the old
XSLPattern language (*default*) as the query language.
Alex
-Original Message-
From: Jamie Thomson [mailto:ja...@jamie-thomson.net]
Sent:
Kevin Burton wrote:
So what does it mean to have DesktopFolder underneath the TARGETDIR. That is
certainly not the hierarchy that is on my computer.
Kevin,
Let me try to explain this one. Think of it as default directory hierarchy
with possibility to override default entirely or partially.
Combination of:
http://blogs.technet.com/b/alexshev/archive/2008/02/14/from-msi-to-wix-part-6-customizing-installation-using-custom-tables.aspx
and
http://blogs.technet.com/b/alexshev/archive/2008/07/01/from-msi-to-wix-part-19-the-art-of-custom-action-part-1.aspx
Should give you an idea on how
Hi Carolina,
Your XPath looks fine. You need to show your XML. Include Configuration
element and its parents in the xml file.
Do you have something like:
DTSConfiguration
...
Configuration
...
/Configuration
...
/DTSConfiguration
-Original Message-
From: Carolina
Add SelectionLanguage attribute to your Util:XmlFile element:
Util:XmlFile ...
SelectionLanguage=XPath /
-Original Message-
From: Carolina Zuqueto Amaral [mailto:carolina.ama...@conv.com.br]
Sent: Thursday, June 17, 2010 3:20 PM
To: General discussion for Windows Installer XML
Your XML is malformed:
ConfiguredValue\\convs07\Historicalfile:///\\convs07\Historical
Integration\DataFarm\WIT\Files\/ConfiguredValue
Should be either:
ConfiguredValue![CDATA[\\convs07\Historicalfile:///\\convs07\Historical
Integration\DataFarm\WIT\Files\]]/ConfiguredValue
Or
That was my first thought too, but according to MSDN
(http://msdn.microsoft.com/en-us/library/aa372021(VS.85).aspx):
A {column-list} is a comma-delimited list of one or more table columns referred
to as {column} selected. Ambiguous columns may be further qualified as
{tablename.column}. An
You mean LogonUser
(http://msdn.microsoft.com/en-us/library/aa369780(v=VS.85).aspx) or something
else?
-Original Message-
From: Carolina Zuqueto Amaral [mailto:carolina.ama...@conv.com.br]
Sent: Friday, May 14, 2010 12:33 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
Looks like this command requires admin privileges. Try changing your CA to be
deferred and run it before InstallFinalize.
-Original Message-
From: Carolina Zuqueto Amaral [mailto:carolina.ama...@conv.com.br]
Sent: Tuesday, May 11, 2010 9:06 AM
To: 'General discussion for Windows
Hi Joseph,
Let's first make sure we use correct terminology. Wix is a tool to create MSI
installers. MSI installer installs, upgrades and uninstalls products and while
doing that, it also creates/deletes folders among numerous other things.
One thing you can use to solve your problem is the
Hi Matt,
I have some information (old because it covers WiX 2.0, but your problem is
more of MSI-related issue) in
http://blogs.technet.com/alexshev/archive/2008/04/04/from-msi-to-wix-part-16-installable-items-handling-installation-media.aspx
I am not 100% sure, don't have time to test it, but
I don't think MSI supports that. See definition of the Icon table
(http://msdn.microsoft.com/en-us/library/aa369210(v=VS.85).aspx)
-Original Message-
From: Sylvain Petreolle [mailto:sylv...@mhzwireless.com]
Sent: Tuesday, May 04, 2010 3:26 AM
To: Wix-Users
Subject: [WiX-users]
, and File/@Compressed=no on just my one external
file. I guess it only works in one direction.
Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com
-Original Message-
From: Alexander Shevchuk (Volt) [mailto:a
http://en.wikipedia.org/wiki/ComSpec
-Original Message-
From: jeff00seattle [mailto:jeff_tan...@earthlink.net]
Sent: Thursday, April 29, 2010 12:03 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Program Menu: Target shortcut is a Directory
Thanks for the reply
I
Seems like there is special procedure to do that:
http://msdn.microsoft.com/en-us/library/ee332502.aspx
Also, documentation is saying that in order to install templates using .vsix,
target system has to have SDK or Visual Studio installed.
As far as WiX code validity, CA declaration looks
In
http://blogs.technet.com/alexshev/archive/2008/02/20/from-msi-to-wix-part-10-shortcuts.aspx
search for Special case - Starting application in the command window, change:
Arguments='/k [!ConsoleApp.exe]'
To:
Arguments='/k'
That will open command window in the folder of your choice.
Good
Hi Jeff,
Let's step back and take a closer look at your code below.
Normally we start directory structure like this:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder
Directory Id=MYAPPLICATIONFOLDER Name=MyProduct
...
/Directory
/Directory
/Directory
By
Target must be this:
Target='[%ComSpec]'
-Original Message-
From: jeff00seattle [mailto:jeff_tan...@earthlink.net]
Sent: Tuesday, April 27, 2010 5:02 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Program Menu: Target shortcut is a Directory
Addendum:
I have
Hi Mark,
MSI packages support three top level actions. Which one of them will be run
depends on the switch we pass to the msiexec utility (I will omit for now MSI
API calls) and that also will determine which sequence tables will be used
during install.
So, when /i switch is passed, MSI will
Hi Markus,
The Source (http://msdn.microsoft.com/en-us/library/aa369210) is saying:
Icon files that are associated strictly with file name extensions or CLSIDs
can have any extension, such as .ico. However, Icon files that are associated
with shortcuts must be in the EXE binary format and must
http://blogs.technet.com/alexshev/archive/2008/03/25/property-does-not-exist-or-empty-when-accessed-from-deferred-custom-action.aspx
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
Sent: Wednesday, April 07, 2010 1:29 AM
To: General discussion for Windows
Hi Sanjay,
Do you have RemoveExistingProducts scheduled?
Alex
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
Sent: Monday, April 05, 2010 12:06 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] version upgrade problem
Hi
:\ drive (CD ROM Drive). If it does then half
problem is solved.
Yes, I wish bootstrapper - I do have it but got to remove it, well requirements
are that we need to install items on demand based on user selection.
Arun Perregattur
-Original Message-
From: Alexander Shevchuk (Volt
Hi Steve,
I guess, SQL attribute is a Formatted string. Try to escape [ and ]:
[\[]
And
[\]]
Alex
-Original Message-
From: Steve Braswell [mailto:sbrasw...@informasoftware.com]
Sent: Monday, December 07, 2009 1:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
Your UnDeploy custom action does not have Execute=deferred attribute, which
means it is immediate CA.
-Original Message-
From: cce91 [mailto:ell...@nortel.com]
Sent: Monday, November 23, 2009 1:55 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] CustomActionData for
Condition element under Product is a LaunchConditions action and usually
LaunchConditions action is scheduled way before FindRelatedProducts action.
What you need is appropriately conditioned Custom Action Type 19 scheduled
right after FindRelatedProducts in both InstallUISequence and
Type of serviceinst...@start attribute is not Formatted
(http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx). So, depending
on when decision has to be made on this attribute's value:
- Build time
Use preprocessor directives to set variable and use it something like this:
When during the uninstall are the RegistrySearch values evaluated?
RegistrySearch is evaluated during AppSearch action.
Are they evaluated during by uninstall package that is invoked during
a major upgrade as well? If so, when?
Uninstall during major upgrade is done by RemoveExistingProducts
Hi Scott,
If this condition does not apply to a component which installs Web.config file,
put util:XmlFile in separate Component and apply condition to it:
Component Id=...
Condition![CDATA[CLIENTNAMESOMECLIENT]]/Condition
util:XmlFile ...
/Component
Basically, Condition is a child of
All custom directories, like SHELLPATH are represented as properties and they
will get their values after CostFinalize (suggested sequence number in
InstallExecuteSequence - 1000). Your Property Id=ISSHELLINSTALLED... - is
an AppSearch (suggested sequence 400) and at the time of AppSearch
You need to use CA Type 35 scheduled after CostFinalize to set MYDIR to
whatever you want.
Alex
-Original Message-
From: Hoang Le [mailto:hoangle2...@gmail.com]
Sent: Thursday, October 22, 2009 3:44 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
Hi Chris,
If you will dark resulting msi (with merge module included), you'll see
something like this:
Directory Id=CommonAppDataFolder.GUID ..
. . .
/Directory
. . .
InstallExecuteSequence
. . .
Custom Action=CommonAppDataFolder.GUID Sequence=1 /
. . .
/InstallExecuteSequence
. . .
Hi Jaspreet,
Move your default web site declaration out of Component to Product.
Alex
-Original Message-
From: Jaspreet Nabha [mailto:jaspreet.na...@headstrong.com]
Sent: Thursday, September 03, 2009 12:50 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Uninstalling
In Wix help file read How To Guides\Updates\How To: Implement a Major
Upgrade In Your Installer
-Original Message-
From: Anu Dev [mailto:queryl...@yahoo.com]
Sent: Thursday, September 03, 2009 9:49 AM
To: WIX
Subject: [WiX-users] WIX Upgrade
Hi
Wanted to know if anyone of you have
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] hoping for confirmation
Ah thank you! I knew I must be missing something simple.
Amy
-Original Message-
From: Alexander Shevchuk (Volt) [mailto:a-ale...@microsoft.com]
Sent: Tuesday, September 01, 2009 11:29 AM
Hi Hicholas,
CopyFile will be translated to a record in the MoveFile table
(http://msdn.microsoft.com/en-us/library/aa370055(VS.85).aspx) and will be
processed by MoveFiles action
(http://msdn.microsoft.com/en-us/library/aa370054(VS.85).aspx). The very last
statement in the MoveFiles Action
Hi Amy,
Did you set UpgradeVersion/@MigrateFeatures to yes on product you want to
upgrade?
Alex
-Original Message-
From: Amy Rosewater [mailto:arosewa...@spectrumhr.com]
Sent: Tuesday, September 01, 2009 9:28 AM
To: General discussion for Windows Installer XML toolset.
Subject:
See Conditional Statement Syntax -
http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx
Ampersand means action to be applied to the feature.
Alex
-Original Message-
From: Arvind Aiyar [mailto:arvind.ai...@microsoft.com]
Sent: Monday, August 31, 2009 11:22 AM
To: General
RemoveFolder will delete only empty folders. If your shortcut is not the
last in the FooBarProgramsFolder, it won't be deleted on your product uninstall.
Alex
-Original Message-
From: Richard Hallett [mailto:richard.hall...@eduserv.org.uk]
Sent: Wednesday, August 26, 2009 9:03 AM
Hi Greg,
If the product is installed, is it possible to uninstall some, but not all
features?
During Change install (in Program and Features, former ARP) users can uncheck
any of the installed features to uninstall them. If no UI is involved, in
command command line provide REMOVE property
-- Forwarded message --
From: Alexander Shevchuk shevc...@live.com
To: 'General discussion for Windows Installer XML toolset.'
wix-users@lists.sourceforge.net
Date: Sun, 26 Jul 2009 10:19:16 -0700
Subject: Re: [WiX-users] conditionally append to a directory
I've scheduled this before CostFinalize
Hi James,
Have you tried the usual XML escaping?
lt;DIRECTIONgt;UPlt;/DIRECTIONgt;
Alex
-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com]
Sent: Monday, July 27, 2009 8:51 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users]
I've scheduled this before CostFinalize.
Directory resolution happens during CostFinalize. You need to schedule your
CA after CostFinalize.
Why are you scheduling your CA before CostFinalize? Any concerns that after
CostFinalize it will be too late to change the installation folder?
Alex
Search for Major Upgrade.
Alex
-Original Message-
From: jo...@msli.com [mailto:jo...@msli.com]
Sent: Friday, July 24, 2009 8:59 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] how to force uninstall before install
I am going thought the process of
Few options available here and you can find more using search engine of your
choice:
Neil Sleightholm's blog:
-
http://neilsleightholm.blogspot.com/2009/01/wix-script-for-major-upgrades.ht
ml
My take on it:
-
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-
As far as Media element, this can help:
http://blogs.technet.com/alexshev/archive/2008/04/04/from-msi-to-wix-part-16
-installable-items-handling-installation-media.aspx
I have suspicion that wxs files created by Paraffin contain fragments and in
order to include content of fragment to resulting
So instead I'm checking for the presence of this file. If it's there, I
want
to fail the install.
Not sure how and when HostDir property gets its value. You might want to
make it public (all uppercase and Secure set to yes) if AppSearch happens
in the InstallExecuteSequence.
Alex
learning.
On Wed, 2009-07-22 at 13:56 -0700, Alexander Shevchuk wrote:
As far as Media element, this can help:
http://blogs.technet.com/alexshev/archive/2008/04/04/from-msi-to-wix-part-16
-installable-items-handling-installation-media.aspx
I have suspicion that wxs files created by Paraffin
Hi Eric,
Directory resolution is done during CostFinalize, way after AppSearch. What
you need to do is save the value of HostDir in the registry as part of your
install. Then, during reinstall/upgrade you can use AppSearch to get saved
value from registry and use it for FileSearch.
Alex
Read about IniLocator table
(http://msdn.microsoft.com/en-us/library/aa369283(VS.85).aspx):
... The .ini file must be present in the default Microsoft Windows
directory.
Also, it's the other way around. Parent element starts search and child
element continues it with what parent found. So,
I just want to add that there is one more option, very similar to storing
property value in registry - storing it in the .ini file and use IniFileSearch.
Murray, thanks for being so kind. I'm glad you found Major Upgrade post useful.
Alex
-Original Message-
From: Michael Osmond
Hi Ben,
Description of DrLocator table
(http://msdn.microsoft.com/en-us/library/aa368331.aspx) states that Path column
has type AnyPath
(http://msdn.microsoft.com/en-us/library/aa367562(VS.85).aspx). Description of
AnyPath mentions that path may contain *properties* enclosed in square
For deferred custom actions you pass parameters through CustomActionData.
See
http://blogs.technet.com/alexshev/archive/2008/03/25/property-does-not-exist-or-empty-when-accessed-from-deferred-custom-action.aspx
for details.
Alex
-Original Message-
From: Rajesh P
This is requirement for ServiceInstall table
(http://msdn.microsoft.com/en-us/library/aa371637(VS.85).aspx). Look for
description of Component_ column:
External key to column one of the Component Table. Note that to install this
service using the InstallService table, the KeyPath for this
There are two issues here. First of all, value provided for ExeCommand
attribute is not a valid XML. Remember that ' characters have to be
encoded:
ExeCommand='-d quot;[INSTALLLOCATION] quot; -f quot;
[TempFolder]eclipse.zipquot;'
Second, it seems like whatever tool is parsing this XML
Hi Colin,
It is:
Property Id=XXX
RegistrySearch Id=YYY ... /
/Property
Condition ...
XXX
/Condition
NOT:
Property Id=XXX
RegistrySearch Id=YYY ... /
/Property
Condition ...
YYY
/Condition
Also, you want Property's Id to be in all uppercase.
The only time when you need CDATA in
Hi Michael,
Make sure you follow all required steps to make major upgrade work. In your
simplified code I see Version attribute hard coded to 0.0.0.0. Also, you did
not provide your Upgrade table and how you schedule RemoveExistingProducts.
It is not obvious from your code if you change
ServiceInstall is already deferred. See Suggested InstallExecuteSequence
(http://msdn.microsoft.com/en-us/library/aa372038(VS.85).aspx) -
InstallServices standard action is scheduled after InstallInitialize.
I am not sure what you mean by constructing exe path during execution.
When UI is in use during installation (UI level is not None), Windows Installer
starts with actions from InstallUISequence table. In case when UI level is set
to None, you still want to schedule custom action in InstallExecuteSequence
table. In that case you may want Execute attribute to be
Based on very limited provided information about your scenario - possibly
incomplete advise:
- schedule your custom action before InstallServices standard action;
- condition your custom action on - fresh install OR component state being
changed to Install Local/Run From Source.
Alex
You are mixing to things in your condition:
- Property Installed is telling us if product is installed or not
- Feature is telling us to what state feature is changing from its current
state
This important to understand because user may select a feature to be installed
during fresh install of
Frank,
I am guessing here, the reason NOT Firebird=0 does not get evaluated to TRUE
is because 0 is not a valid value for a feature state (see
http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx).
This description from Condition table
Hi Colin,
Try this:
- Use AppSearch to set the value of public property, say - SHAREPOINT
Property Id=SHAREPOINT
RegistrySearch ... /
/Property
- Schedule custom action type 35:
CustomAction Id=SetInstallDir Directory=INSTALLDIR Value=[SHAREPOINT] /
InstallExecuteSequence
Custom
Also, regarding registry search.
The way how your RegistrySearch is provided - you are looking for a *value*
SharePoint under SOFTWARE\Microsoft\.NETFramework\AssemblyFolders\. Is that
what you want? I think, you actually want a default registry value (no name)
for the
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Setting Install Location
On Tue, Dec 23, 2008 at 10:55 AM, Alexander Shevchuk
alexander.shevc...@microsoft.com wrote:
Hi Colin,
Try this:
- Use AppSearch to set the value of public property, say - SHAREPOINT
I am pretty sure I did not have this ICE before installing 3.0.4805.0.
Here is an upgrade table I am using:
Upgrade Id=$(var.UpgradeCode)
UpgradeVersion Minimum=$(var.OriginalVersion)
IncludeMinimum=yes
Maximum=$(var.CurrentVersion)
: Alexander Shevchuk [mailto:alexander.shevc...@microsoft.com]
Sent: Thursday, December 11, 2008 16:13
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Invalid ICE61 on major upgrade in WiX 3 (3.0.4805.0)
I am pretty sure I did not have this ICE before installing 3.0.4805.0.
Here
It all depends on where you are getting MSI version and/or where you are using
it. Good starting point for this is:
http://msdn.microsoft.com/en-us/library/aa368280(VS.85).aspx
Alex
-Original Message-
From: Sean Farrow [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 16, 2008 3:13 AM
If you use major upgrades only, you can use third field to indicate the new
version.
-Original Message-
From: Colin Bleckner [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 2:55 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Better way
You may want to use Companion files
(http://msdn.microsoft.com/en-us/library/aa367997(VS.85).aspx) in this
situation.
-Original Message-
From: zett42 [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 10:08 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrade
Title column in Feature table
(http://msdn.microsoft.com/en-us/library/aa368585(VS.85).aspx) has type Text
(http://msdn.microsoft.com/en-us/library/aa372072(VS.85).aspx). Things like
[PROPERTYNAME] are valid in Formatted type
(http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx).
I have not tested it, but maybe the problem is that deferred custom action to
launch executable is asynchronous. Hard to say without seeing the code.
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 04, 2008 10:34 AM
To:
Hi Tony,
What is the layout of your transitive components? What your shortcuts point to
- file or folder? Are shortcuts in the same component as files they point to
(providing that they point to files, of course)? Are you sure that old
components are uninstalled?
Alex
-Original
1. Start Wix.chm
2. Click on Index tab.
3. Type user in Type in the keyword to find.
4. Click on User Element in the list box below.
5. Click Locate on the toolbar.
You will see that User element belongs to Util schema.
1. Add reference to WixUtilExtension
2. Add reference to Wix element to
It is documented on MSDN:
- Custom actions in general:
http://msdn.microsoft.com/en-us/library/aa368066(VS.85).aspx
- Return values (DLL and EXE):
http://msdn.microsoft.com/en-us/library/aa368072(VS.85).aspx
- Return values for scripting CA:
MSDN topic on REMOVE property
(http://msdn.microsoft.com/en-us/library/aa371194(VS.85).aspx) states:
...the REMOVE property may not equal ALL until after the InstallValidate
action.
On the other hand, instead of saying if not fresh install and not uninstall
and not patch and not upgrade just
Remember that UPGRADINGPRODUCTCODE is set by RemoveExistingProducts action. For
your condition for UninstallCA to work properly, RemoveExistingProducts must be
scheduled before your custom action.
REMOVE=ALL means complete uninstall.
-Original Message-
From: chaiguy1337
?
Alexander Shevchuk wrote:
Remember that UPGRADINGPRODUCTCODE is set by RemoveExistingProducts
action. For your condition for UninstallCA to work properly,
RemoveExistingProducts must be scheduled before your custom action.
-
A. Logan Murray
http://pihole.org/
--
View this message
Sorry if that was answered before, in this case I somehow missed it. What
happened to SnapIn, ExtendedNodeType, PublishedNodeType, and Resources elements
in V3?
Thanks,
Alex
-
This SF.Net email is sponsored by the Moblin
If you schedule RemoveExistingProduct *after* InstallFinalize, major upgrade
will touch only components where keypath is different. If you did not change
your performance counters, they should not be uninstalled. Component will be
upgraded regardless of UPGRADINGPRODUCTCODE if keypath is
You can either call MsiGetMode/Session.Mode from custom action or, if you are
using MSI version 4.0, use MsiSystemRebootPending property.
-Original Message-
From: Paul Elsner [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2008 5:45 AM
To: wix-users@lists.sourceforge.net
Subject:
Amit,
That is how major upgrade works. If you want to preserve Config files during
major upgrade you have to either copy files to temp folder before upgrade and
restore them after or you need to write custom action which will read the
changes from the Config files, preserve them somewhere
Srivastava
On 10/19/08, Alexander Shevchuk [EMAIL PROTECTED] wrote:
Amit,
That is how major upgrade works. If you want to preserve Config files
during major upgrade you have to either copy files to temp folder before
upgrade and restore them after or you need to write custom action which
According to The Source
(http://msdn.microsoft.com/en-us/library/aa368072(VS.85).aspx):
Note that custom actions that are executable files must return a value of 0
for success. The installer interprets any other return value as failure.
Are you absolutely, positively sure that your custom
Normally, that registry key holds a ProductName property:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\[ProductName]
So, your choices are either change your ProductName to match original from
InstallShield or keep your current ProductName and remove that InstallShield
registry key.
Hi Ian,
In simplest terms: everything from ?include ...? will end up in your msi
database. Only fragments which are referenced from the main code will be
included in resulting msi database. For example:
File1.wxs:
Fragment
Property Id=Included Value=123 /
/Fragment
File2.wxs:
Fragment
One more thing. Make sure that original installation does not have
ARPSYSTEMCOMPONENT set.
-Original Message-
From: Michael Owings [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 3:28 PM
To: Alexander Shevchuk
Cc: General discussion for Windows Installer XML toolset.
Subject
, 2008 3:55 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] fragments and include files
Alex,
Thanks very much. That is very helpful. That might be worth adding to your very
useful blog. I refer to it almost daily!
Ian
-Original Message-
From: Alexander
I think what you need is a deferred custom action scheduled in between
StopServices and DeleteServices actions. This deferred custom action must call
ChangeServiceConfig api
(http://msdn.microsoft.com/en-us/library/ms681987(VS.85).aspx) to reset
lpServiceStartName and lpPassword to LocalSystem
This is CoreXT question. Send your request to corext internal alias.
-Original Message-
From: Sandeep Gautam (HCL Technologies Ltd) [mailto:[EMAIL PROTECTED]
Sent: Monday, October 13, 2008 12:02 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Integration with Corext
Hi,
http://blogs.msdn.com/oldnewthing/archive/2007/04/13/2106139.aspx
-Original Message-
From: Sandeep Gautam (HCL Technologies Ltd) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 07, 2008 3:59 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Component
Madhavi,
You don't need to include the path and executable name in the ExeCommand
attribute's value. Only parameters for the executable:
CustomAction Id=DoSomething BinaryKey=MyCA
ExeCommand='D:\Samples\EnvironmentConfig.xml RPP BACKUP'
Execute=deferred
Return=check HideTarget=no
Hi Bryan,
Two problems here. First, if you want a launch condition based on successful
search, use just RENDERINGINSTALL. Drop != stuff.
Second, by saying Type=directory you are indicating that search is not done
yet and you want to continue with the search and use the data in the registry,
] launch condition query
Hi:
Basically I have an installation I wrote for the same product, if this
installation exists, a registry key will tell me, I want to run the
uninstallation.
What is the best way of doing this?
Cheers
Sean.
-Original Message-
From: Alexander Shevchuk [mailto:[EMAIL
Hi Yuval,
If you schedule your custom action after CostFinalize, you can use
$MyComponent=2 condition. This means that component is about to be
uninstalled. You also need to add condition if you don't want your custom
action to run on complete uninstall.
More on feature and component states:
http://msdn.microsoft.com/en-us/library/aa369297(VS.85).aspx
http://msdn.microsoft.com/en-us/library/aa370858(VS.85).aspx
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of derekj
Sent: Thursday, September 11, 2008 12:02 AM
To:
Knowing what this warning message is saying would help tremendously in
identifying the problem.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jay H. Cho
Sent: Wednesday, September 03, 2008 12:18 PM
To: wix-users@lists.sourceforge.net
Subject: Re:
Warning message is saying what need to be done:
... Please remove the Id attribute in order to automatically generate a new
package code for each new .msi file.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jay H. Cho
Sent: Wednesday, September 03,
Hi Saurabh,
One of the solutions you might want to explore is Major Upgrade:
http://msdn.microsoft.com/en-us/library/aa369786(VS.85).aspx
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx
Alex
-Original Message-
From: [EMAIL PROTECTED]
1 - 100 of 201 matches
Mail list logo
