With Wix 2.0, I used this:
With Wix 3.0.4429.0, I see this warning:
My.wxs(62) : warning CNDL1085 : The IgnoreModularization element has been
deprecated. Use the Binary/@SuppressModularization,
CustomAction/@SuppressModularization, or property/@SuppressModularization
attribute instead.
It d
I just moved a project from IS 12 to WIX, other than what has been pointed out
below, here is what I did:
1. Created my IS 12 generated msm's
2. Ripped out all the IS tables in the .msm's with ORCA
3. Ripped out all the IS custom actions, binaries, properties, etc... in
the .msm's
al tools around who's strengths are on
UI editing.
3. It is simple:
also set Package/@Compressed="yes" to get everything compressed, or compress
File elements individually.
-Original Message-
From: Bryan Turner [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2008
ou guaranteed a major upgrade. Like I said, it gets tricky.
3. Did you actually specify any Files to be compressed? Either set the
Compress attribute on the File or compress everything by default by setting
Package/@Compress.
-Original Message-----
From: Bryan Turner [mailto:[EMAIL
e a "correct and complete" solution is very, very difficult to
implement.
I'm also curious why you chose to use an Include instead of using a Fragment
with a ComponentGroup in it that is pulled in at link time?
-Original Message-
From: Bryan Turner [mailto:[EMAIL PROTECTED]
Hello, I think I am missing something obvious
I am using Wix 3.0.4429. In my .wxs file, I have the following elements:
When I link with Ligh
Yan,
Try uninstalling from the command line with the option DISABLEROLLBACK=1.
For example, msiexec /x yourmsi.msi DISABLEROLLBACK=1.
This might make the uninstall quicker if it does not need to create copies of
all the files as it removes them in case you hit the cancel button during
uninstal
We have also experienced this issue. Fortunately, we have a
bootstrapper/chainer that allows us to install vcredist_x86.exe and
vcredist_x64.exe instead of merging those modules into our installer directly.
We like this method better as it keeps our installer just a little bit cleaner
and is
One approach to this that I have seen work is where you have one .wxs file that
generates both a 32-bit and a 64-bit .msi through conditional logic. You then
wrap both the 32-bit and 64-bit .msi in a bootstrapper that determines the
correct .msi to install at runtime. The bootstrapper can be p
: Tuesday, October 28, 2008 10:02 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] vc9 mergemodule and long uninstallation times
Bryan Turner wrote:
> We have also experienced this issue. Fortunately, we have a
> bootstrapper/chainer that allows us to i
Chad,
I may not be fully understanding your requirements, but it sounds like you want
to create a patch that does not patch every file in the installer? I have not
yet tried to create patches with WIX, I still use msimsp to create patches with
a .pcp file for the input, so I cant tell you the
11 matches
Mail list logo
