MergeModules don't have a ProductCode. modu...@id is a value that identifies
the module to enable modularization of properties, directories, and whatnot
for the contents of merge modules in MSIs.
You can't influence (except in a negative way) upgrade types from a merge
module. Those are 100%
Installer XML toolset.
Subject: Re: [WiX-users] Upgrade in per-user folder generates double entries
in Add/Remove programs
Thanks Blair.
I set ALLUSERS to 1 in order to install to c:\program files by default
in both setups.
Anyway you're right: I actually don't need a per-user installation.
What I'm
I assume Property
-Original Message-
From: John Bergman [mailto:john.berg...@xpedienttechnologies.com]
Sent: Wednesday, July 21, 2010 9:51 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Passing Values from the ProductModule to a
MergeModule
Even
No. The preprocessor runs as part of loading the WXS files in the candle
tool, and WXL files are not even accessed until either the light tool or the
lit tool, which don't use the preprocessor.
-Original Message-
From: Sharat Janapareddy [mailto:sharat.janapare...@microsoft.com]
Sent:
In your settings for heat, you should use automatic component guids (they
come out as Guid=*) and you should setup a component group for your PDF
files (then you can simply refer to them from your feature using the
ComponentGroupRef element).
-Original Message-
From: Lukas Haase
Registry entries created with an action of 'write' are removed upon
uninstall of the component. The action called 'createAndRemoveOnUninstall'
applies to keys and removes all entries of that key, whether created by
Windows Installer or not, and is not needed in most cases. It is a case of
the name
That could help reduce the chance of that problem, but depending on which
file the user changes (the initial or the update) you may not get a chance
to warn the user to not rename the MSI.
In most of the failure cases I have seen due to not finding the MSI file at
the indicated directory caused
each time, which is the
primary requirement for generating major upgrades).
SourceFile directory: Easiest fix (from my point of view) is to use the -var
switch, and tell the compiler where to look. Something like this:
Heat ... -var PdfFolder ...
Candle ... -dPdfFolder=src\INSTALLDIR\pdf\ ...
Blair
1. You can build MSIs with WiX that don't require running the setup as
administrator. Nothing that can be done outside of Windows Installer without
elevation requires elevation in Windows Installer to also do.
2. Windows Installer has no built-in support for detecting/removing non-MSI
packages.
possible because I have never seen an issue but I mainly stick to
major
upgrade because they are less hassle.
Neil
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 21 July 2010 23:12
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Does the msi
, July 21, 2010 3:27 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Does the msi-filename matter?
Dear Blair, Dear Christopher,
Thank you for your reply.
Am 22.07.2010 00:11, schrieb Blair:
[...]
This is part of the reason huge numbers of software producers distributing
over
If I recall correctly the .inf file must be the keypath of the component
that Difx is installing.
Directory Id=PciIbs Name=PciIbs
Component Id=PciIbsDriver
Guid={AD037B1D-D7B7-4354-A5AB-BED39591ABC8}
File Id=Ibddiwnt.dll Name=Ibddiwnt.dll DiskId=1
Source=Ibddiwnt.dll /
Place your directory under a well-known directory. TARGETDIR defaults to the
root of the drive with the largest free space, so you need some other
directory as a closer ancestor of your directory that Windows Installer
defines to some system-defined folder.
-Original Message-
From: subrat
Two issues:
1st issue (related to both your problem AND the conditions you supplied):
INSTALLED is NOT the same as Installed. Installed is defined by Windows
Installer, INSTALLED is a different property (that is public) that you can
use for whatever you want, but you will need to supply your own
Two components, both associated with the same directory, with different
conditions.
-Original Message-
From: sd dd [mailto:greme4u2...@hotmail.com]
Sent: Tuesday, July 20, 2010 10:15 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] how do i conditional place a file with
Was the value of ALLUSERS property different between the two installations?
Per-machine installations and per-user installations are basically in
separate worlds for Windows Installer and shell components such as ARP
show a combined view of both worlds.
Most programs tend to be either per-user or
As Christopher said:
Property Id=SERVICEUSER SuppressModularization=yes /
Property Id=SERVICEPASSWORD SuppressModularization=yes /
-Original Message-
From: John Bergman [mailto:john.berg...@xpedienttechnologies.com]
Sent: Tuesday, July 20, 2010 4:42 PM
To: General discussion for
Try the Configuration element under Module, and use the ConfigurationData
element under Merge to hook it up.
-Original Message-
From: John Bergman [mailto:john.berg...@xpedienttechnologies.com]
Sent: Tuesday, July 20, 2010 5:17 PM
To: General discussion for Windows Installer XML toolset.
/aa370052.aspx
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Tuesday, July 20, 2010 5:33 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Passing Values from the ProductModule to a
MergeModule
Try the Configuration element under Module
Use ConfigureProduct() in place of ReinstallProduct().
-Original Message-
From: SimonKnight6600 [mailto:simonschwei...@gmail.com]
Sent: Monday, July 19, 2010 6:15 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] DTF: ReinstallProduct with commandLine property
I've developed
not running
The underlying issue is likely to be that UAC systems run impersonated
custom actions without elevation, even if you are an administrator. ON XP
your custom action would be running elevated with admin privs, but not on
UAC, and that's why Blair is telling you how to make it elevated
Status pending in the bug means that the build with the fix has not yet been
generated. The earliest the fix will likely be released is this Friday (the
23rd) in the weekly releases (in a build version 3.5.1922.0 or greater).
-Original Message-
From: Bhaumik Barot
-
From: Blair [mailto:os...@live.com]
Sent: Monday, July 19, 2010 3:26 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Custom Action not running
Then your custom action is likely attempting to access things in the
session/database that deferred
Is there any way to make the HintPath a fully qualified path? Perhaps
something along these lines?
ItemGroup
Ext Include=..\..\path\to\ext.dll/
WixExtension Include=Ext
HintPath%(Ext.FullPath)/HintPath
NameExt/Name
/WixExtension
/ItemGroup
-Original Message-
Three thoughts come to mind:
1. Most of what you are looking for can easily be achieved using Features (a
concept in Windows Installer that WiX supports quite well), although rolling
back would be difficult-to-impossible (all the rest of your requirements
would be relatively easy to meet).
2. If
Also, try running a pure uninstall in quiet mode with logging.
-Original Message-
From: Thomas Svare [mailto:thomas_sv...@symantec.com]
Sent: Saturday, July 17, 2010 5:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RemoveExisting Products failing
Not sure what your logging problem would be, but I suspect that your custom
action does not have the necessary privilege to install drivers.
Have you looked at DifxApp?
-Original Message-
From: Thode, Katelyn [mailto:katelyn.th...@guidancesoftware.com]
Sent: Friday, July 16, 2010 8:17
action being called
for reasons that I won't go into as they are specific to the particular
application. Is there a way to give the custom action the necessary
privilege to install drivers?
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, July 16, 2010 10:40 AM
MSI 4.5 and later allow adding additional product/package transactions from
the MSI itself (via custom actions calling APIs). If you can require MSI 4.5
you can accomplish this without resorting to ARPSYSTEMCOMPONENT. You do have
to write small bootstrapper exes that call certain APIs to use this
MSP application uses the UI from the MSI it upgrades to.
-Original Message-
From: KATO Kanryu [mailto:k.kan...@gmail.com]
Sent: Wednesday, July 14, 2010 11:20 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to add UI for Minor Patches(msp)?
hi,
I made a minor patch with
Use Environment.SpecialFolder.ProgramFilesX86 instead of
Environment.SpecialFolder.ProgramFiles. Both values should be defined on a
32-bit machine.
-Original Message-
From: Chirag Goradia [mailto:chiraggora...@gmail.com]
Sent: Thursday, July 15, 2010 2:46 AM
To:
SourceDir is set by Windows Installer and is a private session property,
so no bootstrapper can easily change it to something different than the
folder the MSI is run from. You could try using a bootstrapper that passes
a property with a value corresponding to its current directory (or adding
It would appear that the preview handler you are using does some
calculations to determine what changes to make to the box (a part of the
evil of self-registration is when there is no way to know beforehand what
some component will try to do to your box).
You will need to get a hold of the source
Here is the list of attributes that Windows Installer allows edit controls
to have:
http://msdn.microsoft.com/library/aa368342.aspx
Readonly isn't one of them.
I haven't tried: can you select and copy text from a static text control?
-Original Message-
From: Elfe Xu
Could it be something related to the executable being launched instead of an
issue with the custom action itself?
What is the impersonate setting of the custom action doing the launching?
What is the executionLevel value for the executable being launched?
-Original Message-
From: Keith
If you simply remove the older version (without installing the newer
version), do the shortcuts remain?
What is your associated code for the shortcuts in both old and new versions?
-Original Message-
From: Thode, Katelyn [mailto:katelyn.th...@guidancesoftware.com]
Sent: Wednesday, July
If you have code that causes the application(s) detected to shutdown
(including using the built-in actions to stop services you install) the
restart manager-related detection code doesn't always acknowledge that. As a
result the user is often told of a need for reboots that ultimately are
never
Could your custom action be written such that it simply exits early with a
success code if it doesn't find the App.Config file?
-Original Message-
From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
Sent: Wednesday, July 14, 2010 8:25 AM
To: General discussion for Windows Installer XML
The product id is set to a guid. I suppose based on that text that the
ProductCode GUID doesn't change between the versions?
FindRelatedProducts and RemoveExistingProducts do not run during maintenance
transactions. A maintenance transaction always runs when the ProductCode of
the current package
get a reboot prompt at the end of the uninstall
or upgrade. But there isn't one. Am I reading the documentation correctly?
Blair wrote:
If you have code that causes the application(s) detected to shutdown
(including using the built-in actions to stop services you install) the
restart manager
, 2010 at 11:06 AM, Blair os...@live.com wrote:
Could your custom action be written such that it simply exits early with a
success code if it doesn't find the App.Config file?
-Original Message-
From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
Sent: Wednesday, July 14, 2010 8:25 AM
===
and it still shows it on both install and uninstall...
I put ALL in quotes, and it DOESNT show it on install... :(
-J
On Wed, Jul 14, 2010 at 12:33 PM, Blair os...@live.com wrote:
Condition the button to be hidden if REMOVE=ALL ?
-Original Message-
From: Jeremy Rimer
, 2010 at 1:11 PM, Blair os...@live.com wrote:
Use MyExitDialog always, and hide the button in that dialog that runs your
CA.
-Original Message-
From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
Sent: Wednesday, July 14, 2010 11:04 AM
To: General discussion for Windows Installer XML
instead of trying to make a custom solution specifically
for Explorer.exe.
Blair wrote:
If you didn't replace one of the files that were discovered to be in use,
then no, you won't get an automatic reboot prompt. Which file did you
replace when you uninstalled your application?
-Original
Update Users
Guide.pdf
UninstallProductTFirmwareUtilFolder z2qb0bcp|Uninstall Firmware
Update ShortcutComponent [System64Folder]msiexec.exe
Again, thanks for your help.
Katelyn
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Wednesday, July 14, 2010 10:41
).
-Original Message-
From: i...@roadrunner.com [mailto:i...@roadrunner.com]
Sent: Wednesday, July 14, 2010 12:16 PM
To: General discussion for Windows Installer XML toolset.
Cc: Blair
Subject: Re: [WiX-users] Restart Manager (reboot after uninstall)
OK, so basically you are saying
!
The new version does remove its shortcuts.
If I use the RemoveFile element on an update, if the file doesn't exist when
it tries to remove it, will an error occur?
If so, how do I check to verify that the files do exist?
Thanks,
Katelyn
-Original Message-
From: Blair [mailto:os...@live.com
If your setup stub file is similar to setup.exe, you can use setupbld.exe to
configure your setup file you use to replace the wix-supplied setup.exe stub
file.
-Original Message-
From: Durwin Wright [mailto:durwin.wri...@ingres.com]
Sent: Wednesday, July 14, 2010 11:48 AM
To: General
The custom actions used in the WixSQLExtension do not have the
no-impersonate bit set, so they never run as LocalSystem (except in the
rare instance that the installation were being performed by a service
running as LocalSystem). Thus, if you are using the WiX-supplied SQL support
you must launch
Since you are allowing patch upgrades, it is the responsibility of your
bootstrapper to validate that no downgrade is occurring when applying a new
package with the same ProductCode as an already installed package. You must
make sure that your bootstrapper is up to the task.
-Original
In a verbose installation log, what is the resulting value of the TestCA
property?
-Original Message-
From: daniel.knoep...@noser.com [mailto:daniel.knoep...@noser.com]
Sent: Tuesday, July 13, 2010 8:24 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Accessing Source
[mailto:jeremyri...@gmail.com]
Sent: Tuesday, July 13, 2010 12:36 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] WIX Upgrade configuration
I've solved my App.Config issues with help from Blair (Thanks, buddy!!!),
but now I'm running into upgrade path problems
When supporting downgrades, set the REINSTALLMODE property. Specifically,
out of the following set of letters, you want either d or a: a, c, d, e, o,
p. Thus, a good value to use would be amus.
-Original Message-
From: Rob Hamflett [mailto:r...@snsys.com]
Sent: Monday, July 12, 2010 6:29
When you add rows to your table, do you make a reference to one of the items
in your wixlib? That is usually needed to cause the appropriate fragments to
be included when your schema is translated into table entries.
The usual way is in your C# code use the CreateWixSimpleReferenceRow()
method on
Dialogs read values from the UI session. If the custom action runs in the
InstallUISequence then the properties will be available. If the custom
action runs in the InstallExecuteSequence, then those properties will not be
available to the dialogs, since properties only flow from the UI to the
GetLibrary simply adds the library to the other compiled wix code that light
uses to link. There has to be some reference from somewhere for light to not
throw out the fragment as unreferenced. That is the reason most compiler
extensions use CreateWixSimpleReferenceRow to create references to
Changes to non-public properties are never copied from the UI sequence to
the Execute sequence. All properties you intend to set in the UI sequence
and use to influence the Execute sequence must be both public and secure.
-Original Message-
From: Elfe Xu [mailto:elf...@microsoft.com]
Use the heat tool?
-Original Message-
From: David Thielen [mailto:da...@windward.net]
Sent: Friday, July 09, 2010 4:35 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] COM registration of a DLL
Hi;
What's the easiest way to have WIX perform COM registration of a DLL?
If you are not using MSBuild/VS/Votive/Nant, you need to add -ext
WixUtilExtension to both your candle.exe and light.exe command lines.
If you are using any of those build systems, look for how to reference WiX
extensions in the appropriate nant build file or wixproj file (or properties
window,
In your Package element, add an InstallerVersion attribute and set its
value to 300.
-Original Message-
From: amarnath.chakaravar...@cognizant.com
[mailto:amarnath.chakaravar...@cognizant.com]
Sent: Thursday, July 08, 2010 4:29 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
See the MigrateFeatures attribute to the UpgradeVersion element.
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
Sent: Thursday, July 08, 2010 5:45 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] how to select the previously
This has been discussed in this list many times before. You need to set your
property to the new value of the property when the action returns before
using it in the dialog.
Control Type=PushButton Id=Validate Width=56 Height=17 X=234
Y=243
TextValidate/Text
Condition
You can use either a DTF custom action or C/C++ in a custom action dll to
create the temporary rows. If you use C/C++, I recommend using the WCA
library that ships with WiX. Either way, you are making a custom action.
-Original Message-
From: Keith Hassen [mailto:keith.has...@gmail.com]
Did you run the extension in the debugger and verify that it was really
returning an object (and not null)?
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: Thursday, July 08, 2010 10:13 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Compiler
for installation it won't overwrite a future package.
Otherwise, you should always replace every file no matter what on every
installation (allowing complete downgrades) to prevent mixed version
installations.
Blair
-Original Message-
From: Miller, Craig [mailto:craig.mil
Add an additional RemoveFolder element targeting ProgramMenuDir in your
ProgramMenuDirMonarch component. There is no limit to the number of
RemoveFolder elements you can have in the same component.
-Original Message-
From: subrat agasti [mailto:subrat.w...@gmail.com]
Sent: Wednesday,
the unbound wixout and the pdb from the bound
version to create patches against.
Thanks,
Matt
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Wednesday, 7 July 2010 10:11 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] WixUILicenseRtf broken
Actually I think what needs to be done is to add the -svb6 option to
heat's command line. The items that are asking for the SystemFolder happen
to be related to the VB6 runtime.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Wednesday, July 07, 2010 4:57 AM
My recommendation would be to add an immediate custom action in the
InstallExecuteSequence table before CostInitialize that adds temporary
rows to the DuplicateFile table and temporary rows to the Directory table.
You would also need the following authoring:
InstallExecuteSequence
Use CreateFolder. It doesn't hurt anything to ask for a folder to be created
that will be created anyway.
-Original Message-
From: Alec Siu [mailto:alec@microsoft.com]
Sent: Wednesday, July 07, 2010 2:37 PM
To: WiX Users List (wix-users@lists.sourceforge.net)
Subject: [WiX-users]
?
Thanks for your reply.
Blair wrote:
Do the services happen to be marked Interactive?
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
Sent: Monday, July 05, 2010 10:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] services
I am the Blair from that email thread you referenced for the call light
twice technique. That technique was tested without any WixVariable usage.
However, I believe the wixout file should have all required fragments from
the extensions, so I would hope that the extensions could be dropped from
The platform support for products such as Narrator is called Accessibility
by Microsoft. This page gives the guidelines for that support for Windows
Installer UI: http://msdn.microsoft.com/library/aa367454.aspx
Basically, you need to have a Text type control that provides the caption
for each of
-
From: Matt Sullivan [mailto:msulli...@zaptechnology.com]
Sent: Tuesday, July 06, 2010 3:01 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixUILicenseRtf broken when binding sources into
wixpdb
Thanks for your help Blair, however excluding the extensions
Simply make sure that this plugin's component now points to the location you
now wish it would install into, and supply the new component definition to
the customers MSIs. When the products are upgraded, the old components will
be removed. Unless you control the installation sequence of the
You will need a modified version of (a subset of) WixUtilExtension.
-Original Message-
From: Elfe Xu [mailto:elf...@microsoft.com]
Sent: Sunday, July 04, 2010 11:17 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Inherit permissions on a folder in WiX 3
Then how to make
You can't run a deferred action from a Publish. If you use cmd.exe (or
QAQuietExec) you may be able to launch the executable in such a way as to
let UAC prompt you for elevation. The failure is because CustomAction
FileKey/ launches in such a way as to not allow UAC to be invoked, and the
Yes. You indicate which dialog is next based on those conditions.
In each of those two dialogs, use similar conditions for the back button to
get the correct dialog when going backwards.
-Original Message-
From: Jon Hardcastle [mailto:jd_hardcas...@yahoo.com]
Sent: Monday, July 05, 2010
Yes. You indicate which dialog is next (based on your conditions).
-Original Message-
From: Jon Hardcastle [mailto:jd_hardcas...@yahoo.com]
Sent: Monday, July 05, 2010 4:42 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Altering Application Flow
Guys,
Is it
at all.
Unlike many other programming languages, a cleared variable in Windows
Installer is NOT the same as the value 0.
From: Kagiso Seboni [mailto:kagisoseb...@yahoo.com]
Sent: Monday, July 05, 2010 12:14 PM
To: Blair Murri
Cc: wix-users sourceforge
Subject: Re: [USEINTEGRATEDSECURITY
Create an immediate custom action that calls GetPrintProcessorDirectory()
and sets the property PrintProcessorDirectory with that location (appending
it with a \ character if it doesn't already end with one). Schedule that
custom action in the InstallExecuteSequence table someplace before
Do the services happen to be marked Interactive?
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
Sent: Monday, July 05, 2010 10:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] services stops at logoff
Hi All,
I have a
above).
Blair
-Original Message-
From: Ivo Beltchev [mailto:i...@roadrunner.com]
Sent: Saturday, July 03, 2010 7:29 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Question about Start Menu shortcuts
Hi
I have an installer with 2 features. Each feature
It would depend on the particular virtual machine implementation. A solution
for Hyper-V would be different than one for VMware, which would be different
than one for Virtual PC, which would differ from one for Xen, which would be
different than Parallels, etc.
-Original Message-
From:
Look at heat.
-Original Message-
From: Charlie Arcuri [mailto:charc...@microsoft.com]
Sent: Sunday, July 04, 2010 3:17 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] specifying source folder *and everything underneath it*
- possible?
I'd like to specify a single source
PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Unable to add permission for virtual account
Thanks Blair!
Yes, the util:PermissionEx works fine. And to my surprise, it works on my
Vista machine with WI4.0 as well. (I've changed the account to NT
Authority\LocalService
This has been submitted as bug 3024936.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Tuesday, May 25, 2010 3:31 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Using document() function in XSLT with HEAT
To contribute it back, you
This has been much discussed on this list. One such thread starts here:
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg30266.html
-Original Message-
From: Chirag Goradia [mailto:chiraggora...@gmail.com]
Sent: Friday, July 02, 2010 4:35 AM
To:
Then you just broke the component rules and you enter this mess all over
again. Even worse, since the old GUID no longer exists in your updated minor
upgrade package, your component's installed feature(s) will be advertised
without being physically removed from the machine (because Windows
Silly question: does it work if you use Permission GenericAll=yes
Domain=NT Service User=MyService /
-Original Message-
From: Elfe Xu [mailto:elf...@microsoft.com]
Sent: Friday, July 02, 2010 7:17 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Unable to add permission for
;
and reference the WixUtilExtension.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, July 02, 2010 12:03 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Unable to add permission for virtual account
Silly question: does it work if you use
This is my personal opinion, since I didn't write that code. However, given
what I have seen of the code, it seems quite reasonable (at least to me ;-)
).
Because the property TEST may be found in a Condition, a formatted field,
or who knows where else a reference to the item may be within the
Whenever I see someone trying to do something that a built-in action does
quite well, I recommend this concept:
http://www.joyofsetup.com/2007/07/01/semi-custom-actions/
Why reinvent the wheel? Windows Installer does a fantastic job writing
registry entries and removing them later on under all
It is, if there aren't orphaned products left behind.
First step: what does the verbose log from the upgrade say?
-Original Message-
From: Stelios Kyprou [mailto:stelios.kyp...@formicary.net]
Sent: Thursday, July 01, 2010 10:06 AM
To: General discussion for Windows Installer XML
@lists.sourceforge.net
Subject: Re: [WiX-users] ServiceInstall and ServiceControl question
Hi Blair,
Would you please help me to understand why I need to make the CA as deferred
without impersonation?
Since I want the install to success no matter whether the service started
successfully or failed, I just run
Both components are in the same fragment. Thus, they will both be patched. I
answered this question recently in this list.
The following has each component in separate fragments, which will allow
them to be patched separately.
Fragment
DirectoryRef Id=SampleProductFolder
With regards to files that don't have Version resources (since WiX's binder
by default does populate the file hash for files that don't contain version
resources) the following pages are of use to help you understand what is
expected.
The default behavior for your case is described on this page:
For localization, if you don't want the localizers to mess up the bolding,
do this instead:
*.wxl
...
String Id=MyDlgTitleCreate Virtual Directory/String
...
*.wxs
...
Control Id=Title Type=Text X=15 Y=6 Width=200 Height=15
Transparent=yes NoPrefix=yes
ServiceControl Start=install Stop=both/
-Original Message-
From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com]
Sent: Tuesday, June 29, 2010 2:00 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Stop service when patching
How do you stop and then restart windows service when
Place the SampleComponent component in its own Fragment.
-Original Message-
From: Sunkesula, Srivardhan [mailto:srivardhan.sunkes...@netapp.com]
Sent: Tuesday, June 29, 2010 2:57 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] patching a single file
Hi,
801 - 900 of 1942 matches
Mail list logo
