You should change version of the file which is included in the patch.
-Original Message-
From: Jeanne Dixon [mailto:jdi...@cots.com]
Sent: Wednesday, August 01, 2012 7:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Assistance with creating a patch
Any help will be appreciated.
Thanks,
Maksim
-Original Message-
From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com]
Sent: Monday, June 25, 2012 3:00 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] x86 x64 vc runtime merge modules installation problem
Hi All,
Hi All,
Recently I faced the following issue with installation of x86 and x64 merge
modules on a host: installation on Windows Server 2008 SP1 fails with the
following errors:
Component Based Servicing (CBS) log:
...
Session: 30232391:1539712812 finalized. Reboot required: yes
2012-06-20
MSI of our product which is built with WiX uses UI localization from WiX and
some functions which are implemented in WiX libraries (like quite execution).
The question is whether there is any possibility to get some version of WiX
(3.5, maybe somehow restricted) with non-CPL license?
Rob, could
Dear Sirs,
We are considering WiX as a platform to build our installers. We have completed
prototyping and it has been proven that WiX can significantly simplify our
installation codes using custom WiX extensions.
The only issue that we have to sort out before switching to WiX is the CPL
Hi,
Is there any way now to download full package for WiX 3.6.beta installation
(which doesn't try to download something during the installation)? I tried to
install Wix36.exe but it failed with the following error:
Error 0x80070002: Failed to download payload from
Hi All,
Recently on one host the installation started to fail with error 2203 when it
is being installed by a script; when I run the installation manually it runs
without any problems. Here is the complete verbose log:
=== Verbose logging started: 10/11/2011 0:57:06 Build type: SHIP UNICODE
You can simply use [SystemFolder] for 32-bit package and [System64Folder] for
64-bit package.
?if $(var.Platform) != x86 ?
?define System32Dir = System64Folder ?
?else?
?define System32Dir = SystemFolder ?
?endif ?
Shortcut
Id=SC_Debug
Name=Pathfinder Service Debug
Try to set LOGVERBOSE=1 property to see the verbose logging of QuietExec. Try
to print the full path of the executed binary before calling QuietExec,
probably the path is incorrect.
-Maksim
-Original Message-
From: Anand, Animesh [mailto:animesh.an...@igatepatni.com]
Sent: Monday,
Instead of MessageBox it's better to use WcaLog(LOGMSG_VERBOSE, Your message).
Here is a working example of using QuiteExec():
LPWSTR pwzCommand = NULL;
LPWSTR pwzSystemFolder = NULL;
hr = WcaInitialize(hInstall, MyCA);
ExitOnFailure(hr, failed to initialize);
hr = WcaGetProperty(LSystemFolder,
The problem in your code is : QuietExec((LPWSTR)(cmdToEx.c_str()),1000);. You
can't transform char* to LPWSTR this way.
-Maksim
-Original Message-
From: Anand, Animesh [mailto:animesh.an...@igatepatni.com]
Sent: Monday, July 25, 2011 1:58 PM
To: General discussion for Windows Installer
One example is to fix the cached .msi during upgrade before
'RemoveExistingProducts' if some bug was found in the uninstallation of the
previous version, or execution of some actions will prevent the upgrade.
-Original Message-
From: Sean Dockery [mailto:dockerys...@gmail.com]
Sent:
You need this:
?if $(var.Platform) != x86 ?
?define Win64 = yes ?
?else?
?define Win64 = no ?
?endif ?
Component ... Win64=$(var.Win64)
-Maksim
-Original Message-
From: Ravi Gupta [mailto:ravigupta...@gmail.com]
Sent: Tuesday, July 19, 2011 2:32 PM
To:
Hi Zong,
I think you can try to search for the answer in the wix*.targets files (in
c:\Program Files\MSBuild\Microsoft\WiX\v3.5\ folder). Here is a description of
the AssignCultures target which seems to set the output folder for each
culture.
AssignCultures
Determines the final list of
You can create separate components and use component conditions to install only
the one which is needed for each OS.
-Maksim
-Original Message-
From: Preethi S. [mailto:preet...@amiindia.co.in]
Sent: Friday, May 13, 2011 1:37 PM
To: General discussion for Windows Installer XML toolset.
Hi Aaronc,
WiX preprocessor does not support recursive variables. You can write a
preprocessor extension for this purpose.
If you have a rather big common part for different modules (with Porperties,
CustomActions, CustomTables) you may think about using .wxi files (pass
parameters to it by
Try
REINSTALL SomeFeature
Also remember that such comparisons are case-sensitive.
-Original Message-
From: Leo ... [mailto:dangle...@hotmail.com]
Sent: Friday, April 22, 2011 12:21 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] condition for feature being reinstalled or
Change REINSTALLMODE property.
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Thursday, April 14, 2011 4:26 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX force copy file.
How do I mark a file 'versioned' so it will
Try to use condition UPGRADE_FROM_VERSION = 6.1.8.85. Not sure it will fix
your problem. Better approach is to use Upgrade element to find previous
versions of your product, and then use properties which are set by
FindRelatedProducts.
-Maksim
-Original Message-
From: Greg
Check that UPGRADE_FROM_VERSION is set during silent installation.
-Original Message-
From: Greg [mailto:g...@swansonsoftware.com]
Sent: Tuesday, April 12, 2011 3:44 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Component condition question
Hi:
I have a component with
You can change REINSTALLMODE to always reinstall files during upgrade.
-Original Message-
From: Michael Tissington [mailto:michael_tissing...@ciqual.com]
Sent: Monday, April 11, 2011 3:39 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] Supporting
Check which files are in use during your upgrade. Replacement of files in use
requires a reboot.
-Original Message-
From: Michael Tissington [mailto:michael_tissing...@ciqual.com]
Sent: Monday, April 11, 2011 4:18 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject:
INSTALLDIR has to be defined in this way:
Directory Id=INSTALLDIR Name=YourProgramName
-Maksim
-Original Message-
From: Michel [mailto:mic...@acromania.nl]
Sent: Monday, March 28, 2011 10:33 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to
It seems like INSTALLSIR isn't defined in your project. You can also use
[#FileID] for full path of your file.
-Maksim
-Original Message-
From: Michel [mailto:mic...@acromania.nl]
Sent: Monday, March 28, 2011 9:03 AM
To: General discussion for Windows Installer XML toolset.
Subject:
Yes, during the build the output directory always will be clean for a new
build. So it will be safe to use cab, if it will be found.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Sunday, February 13, 2011 7:42 PM
To: General discussion for Windows Installer
We do not need different paths for cab cache and output directory. There is no
use cases to store cab cache between builds (when some binary can be changed).
Now our build system manages the build process and the binaries' build, and
installer package creation are different steps for the build
It was just a little block of build log, maybe it was confusing. Build is ok.
Snapshot views are certainly good for it, but I also want to make it faster on
dynamic views.
Is it possible to introduce something like '-forcesreusecab' command line
option for light.exe to skip files' validation
Robocopy to a temp directory is not a very good solution for it... There can be
problems, if many people will build package at one time on a build server,
there can be not enough space in %temp% directory.
Maksim.
-Original Message-
From: Christopher Painter
The main point is to reduce the time of nightly builds which run on dynamic
views. So I don't argue that snapshots are good, but I also want to make
dynamic views better:)
Rob, will an option '-forcereusecab' (or something like that) be considered as
an improvement for light.exe (so I will
Chris, I have no problem with the build itself. But now it takes ~6 min for one
package instead of ~2 (when the build runs for 3 platforms for 2 build types,
it is a big delay..).
Rob, I think the problem here is that light.exe validates the timestamps for
all files each time, and on clearcase
Hi all,
Is there a way to make light.exe correctly work with '-reusecab' option on
dynamic views? Cabinet file is generated for each culture even with '-cc
/cach_path/ -reusecab'.
Thanks,
Maksim.
Build log:
Target Link:
M:\vazhem_wix_boot_from_san\thirdparty\opensrc\wix\3.5\Light.exe
Try to set full paths for cmd and pkgmgr. You can also try to use WiX Quiet
Execution Custom Action, it will show output of the command line in the log (to
see verbose log from WiX ca set LOGVERBOSE=1 on command line).
Maksim
-Original Message-
From: kim [mailto:contactme...@gmail.com]
Thank you for your replies. It helped to solve the problem.
Maksim
От: Maillet, Ed [email...@unum.com]
Отправлено: 28 января 2011 г. 21:43
Кому: General discussion for Windows Installer XML toolset.
Тема: Re: [WiX-users] Building extension .csproj
Here
Hi all,
Is there any way to build C# part of WiX compiler extension using only WiX sdk,
without building needed WiX binaries? Now I have to build WixBuild.dll, because
it is required by WixBuild.Common.targets. I have to use
WixBuild.Common.targets to build the extension because there are some
I'm not very familiar with .NET projects. I need to integrate the build of C#
projects to our build process (based on msbuild). Now it is done by running
.csproj (with import of WixBuild.Common.targets) from another .proj using task
MSBuild. Could you please provide me a sample of .csproj for
Maybe you should hide the feature C from user, and in the
InstallExecuteSequence run a custom action to change the state of the feature
C (it can be made with MsiSetFeatureState function) according to the install
states of other features (you can get feature state with MsiGetFeatureState
The entry in the log
MSI (c) (7C:10) [08:01:24:535]: Skipping action: SetCONFIGREQUIRED (condition
is false)
is written when the custom action runs during InstallUISequence, and
MSI (s) (5C:2C) [08:01:43:082]: PROPERTY CHANGE: Modifying CONFIGREQUIRED
property.
is written during
Read WiX documentation.
'Sequence' attribute controls which sequences the Property assignment is
sequenced in. For 'execute', the assignment is scheduled in the
InstallExecuteSequence. For 'ui', the assignment is scheduled in the
InstallUISequence. For 'both', the assignment is scheduled in
You have to run SetProperty custom action AFTER the dialog in which user
selects all features he wants, not after CostFinalize. Now you set the property
when you don't know what will be installed.
Maksim.
-Original Message-
From: Simon Topley [mailto:simon.top...@mwhsoft.com]
Sent:
Conditions
SetProperty ...$cWIAServices=3/SetProperty
and
SetProperty ...feWIA=3/SetProperty
should work correctly.
Maksim
-Original Message-
From: Simon Topley [mailto:simon.top...@mwhsoft.com]
Sent: Thursday, January 20, 2011 1:03 PM
To: wix-users@lists.sourceforge.net
Subject: Re:
From Windows Installer documentation:
The InstallUISequence table lists actions that are executed when the top-level
INSTALL action is executed and the internal user interface level is set to full
UI or reduced UI. The installer skips the actions in this table if the user
interface level is set
In our product we are moving from InstallShield to WiX. In the current
installer 3082 LCID is used (among others).
Is it save to use WiX Spanish localization for it? Or some additionally check
for this is required?
Thanks,
Maksim.
От: Tobias S
Hi All,
I'd like to clarify LCIDs of the supported languages of WixUIExtension.
Table of LCIDs from MSDN
(http://msdn.microsoft.com/en-us/library/0h88fahh(v=vs.85).aspx):
Locale description
Short string
Hexadecimal value
Decimal value
...
...
...
...
Chinese - China
zh-cn
0x0804
2052
Hi All,
I'd like to clarify LCIDs of the supported languages of WixUIExtension.
Table of LCIDs from MSDN
(http://msdn.microsoft.com/en-us/library/0h88fahh(v=vs.85).aspx):
Locale description Short string Hexadecimal value
Hi,
I am working on a project that required a simple bootstrapper to install
pre-requisites (vcredist, without any conditions), let user to choose
language of the installation and run appropriate .msi package. Is there
a simple way to do it with today's version of Burn? It seems like common
Hi,
I am working on a project that required a simple bootstrapper to install
pre-requisites (vcredist, without any conditions), let user to choose
language of the installation and run appropriate .msi package. Is there
a simple way to do it with today's version of Burn? It seems like common
Thanks. I will enter a bug. I already built it myself, but it will be better to
use this library from SDK, to always have up-to-date version.
От: Bob Arnson [mailto:b...@joyofsetup.com]
Отправлено: Чт, 02.09.2010 8:34
Кому: wix-users@lists.sourceforge.net
Тема:
47 matches
Mail list logo
