Is it reasonable to allow PayloadGroupRef as a child for Bundle? Got the
below mentioned configuration where I didn't see the temporary extracted
payload in file system + log file (and so was spending some time in
investigating).
IMHO Payload Element and PayloadGroupRef Element should have same
Thank your for all the suggestions. I had already included many of the
suggestions into the original installation. I am now in the process of
determining why this occurs on only a few machines while others work fine. I
just don't know what environmental settings could be causing such a drastic
Hello,
is there any way how to insert variable value into DownloadUrl string in run
time of bootstrap? I'm starting bootstrapper from command line like
bootstrapper.exe ServerAddress=192.168.0.11 and I want result on DownloadUrl
line something like:
Antivirus or index server are favourites.
-Original Message-
From: Dexter [mailto:d8x...@hotmail.com]
Sent: 15 April 2013 15:33
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Slow Installs
Thank your for all the suggestions. I had already included many of the
suggestions
Start with CPU, Memory, Disk I/O performance counters. Where is the
bottle neck? Perhaps there is high memory demand with a lot of paging,
perhaps there are other processes hitting the I/O and your disk queue is
pegged. Perhaps it's a heavily fragmented hard drive or a VM that's on an
This is very insightful, thanks! So my MajorUpgrade tag looks like this:
MajorUpgrade AllowDowngrades=yes Schedule=afterInstallInitialize /
The WiX manual ( http://wix.sourceforge.net/manual-wix3/major_upgrade.htm )
says that the Schedule=afterInstallInitialize puts the
RemoveExistingProducts
No, but a custom BA can provide the DownloadUrl for payloads.
On Mon, Apr 15, 2013 at 7:57 AM, Snoza, Ivo ivo.sn...@ncr.com wrote:
Hello,
is there any way how to insert variable value into DownloadUrl string in
run time of bootstrap? I'm starting bootstrapper from command line like
Yes. Curious why you want to support downgrades? Don't hear that very often.
On Mon, Apr 15, 2013 at 8:51 AM, Alain Forget afor...@cmu.edu wrote:
This is very insightful, thanks! So my MajorUpgrade tag looks like this:
MajorUpgrade AllowDowngrades=yes Schedule=afterInstallInitialize /
The
I think that using downgrades to support a rollback scenario is slightly
dangerous in that the user may not realize that they are putting an earlier
version on as it just gets on with it.
Most people block downgrades and let their users un-install and re-install an
older version or have any patch
I want to allow downgrades in case we push out a new version that is flawed in
some way, and it's non-trivial to quickly fix and publish a new version. In
this case, I want to be able to quickly rollback to the previous version that
didn't have the flaw.
It occurs to me now that this may be a
My general experience is that in case of an issue:
It's unusual for all customers to be affected, usually a few, sometimes just
one. It's not difficult to focus a team on the problem and get a detour
followed by a hotfix patch, the more important the customer the higher the
priority. Most
Our software runs in the background with little to no user interaction. When
users go to install our software, we will direct them
to a page that will immediately serve the current version, so I don't think
users even could install an older version. Even if they
did, when the software talks to
Hmm, you've all made some excellent points. I'm definitely glad I asked for
input. I'm sufficiently convinced that allowing
downgrades is more of a complication than it's worth, so I'm going to return to
disallowing downgrades. Thanks again for the
insightful discussion!
Alain
-Original
I have made a custom installer in WIX in order to install the popular app
called BGInfo.
What it does is the following:
1)Create c:\Program Files\BGInfo and put 4 files in it.
2)Create a Folder on the start menu with a link to the application and a link
to uninstall it
3)Create the appropiate
Hi I am Bit struck on setting the condition on component.
Component Id=cmp39F4D3AA1248B5FE5EB2F92D189B27E1
Directory=dirCFCE6D07D3330FE628276777F0488B18
Guid={56788F77-A729-47CE-BBA4-9D7D7F175536}
File Id=fil10B3B7732D0DDBD4AA773E0B7F34D092 KeyPath=yes
Sounds like your InstallExecute sequence is depending on something in your
InstallUISequence. You could verify this with an install from the command line
passing /qn.
-Original Message-
From: Francisco Leon [mailto:fl...@seguroscatatumbo.com]
Sent: Monday, April 15, 2013 1:01 PM
To:
I tried msiexec /i bginfo.msi /qn and everything works fine without any UI, my
suspition is that this is a kaspersky bug since not even the tutorial Project
works.
Here is my whole WXS file.
?xml version='1.0' encoding='windows-1252'?
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
I have made a fake installation that I can't uninstall anymore, is there a way
to force uninstall without creating a new setup bundle with the same
UpgradeCode and manage the upgrade of the old package?using the Windows
installer cleanup utility could be a good way or is there a better way for
Classification: Public
Find the GUID from HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Then in a cmd window run msiexec.exe /x {GUID}
Steve
-Original Message-
From: Marco Tognacci [mailto:mark...@live.it]
Sent: April-15-13 3:08 PM
To: wix-users@lists.sourceforge.net
Subject:
You may need to say what can't uninstall means. Does it crash and rollback
because of a custom action, or something similar? Have you forgetten the
ProductCode?
Phil
-Original Message-
From: Marco Tognacci [mailto:mark...@live.it]
Sent: Monday, April 15, 2013 12:08 PM
To:
I have think about this problem, if I make a mistake in the setup and for some
reason when I have distributed the setup to customers the setup fail to
uninstall (for example it could not show the uninstall button on the custom
UI). How can I make the customer uninstall the product in a way as
Is there any king of automatic tool to optimize the code generated by Heat to
make the file ordered in the way they are located in folders?I have many
fragment files generated by heat based on the same folders, so it wil be
usefull to have the file named with the folder path in which they are
Search for msizap.exe on the msdn website.
On Apr 15, 2013, at 4:03 PM, Marco Tognacci mark...@live.it wrote:
I have think about this problem, if I make a mistake in the setup and for
some reason when I have distributed the setup to customers the setup fail to
uninstall (for example it
Hi,
I have custom bootstrapper where I need to be able to control which MSI
packages in the chain are uninstalled via the UI. It doesn't see like there is
a UninstallCondition like InstallCondition. How would I go about controlling
the behavior?
Thanks,
Sarvesh
I would say fix your MSI, If you release a bad one, you need to re-release it
with the same product/upgrade codes (and version), and have the user recache
your updated MSI and then remove it (ala the fixed MSI).
-Original Message-
From: Mr GAPearce [mailto:mr_gapea...@yahoo.com]
Sent:
If you have a managed bootstrapper, you can collect all the information on your
custom UI and then in the PlanMsiFeature callback you can set the state
(FeatureState = Absent or Local) of the msi feature you want to
install/uninstall, and in the PlanPackageBegin callback you can set the state
msizap creates more problems than it's worth.
On Mon, Apr 15, 2013 at 1:42 PM, Mr GAPearce mr_gapea...@yahoo.com wrote:
Search for msizap.exe on the msdn website.
On Apr 15, 2013, at 4:03 PM, Marco Tognacci mark...@live.it wrote:
I have think about this problem, if I make a mistake in the
+1 but I'd rev the 4th number of the version to know if the user has the
fixed MSI.
On Mon, Apr 15, 2013 at 2:06 PM, Hoover, Jacob
jacob.hoo...@greenheck.comwrote:
I would say fix your MSI, If you release a bad one, you need to
re-release it with the same product/upgrade codes (and version),
I have a msi that installs fine. But if msi is invoked by a Wix setup, I get:
Exception thrown by custom action:
System.Reflection.TargetInvocationException: Exception has been thrown by the
target of an invocation. --- System.IO.FileNotFoundException: Could not load
file or assembly
Well it worked once in a row for me! (with a very simple msi) .
It is quick and (extremely) dirty for a development VM that you forgot to
take a snapshot of, but I would never say use it where it matters if the
machine is usable afterwards.
--
View this message in context:
Yeah, testers used to find crazy bugs with installs. Then a couple hours of
complete confusion trying to figure out what the heck went wrong, they'd
say, Oh, by the way I ran msizap on the machine before the install. As
calmly as possible I'd respond, Cool, format machine and try to reproduce
the
Using Wix 3.7, I have created a default burn bootstrapper using the
WixStandardBootstrapperApplication.RtfLicense. I have been testing through
the behavior of the functionality and noticed the following. If I install the
.msi file directly without using the burn bootstrapper, when I
I have custom bootstrapper and I want to present a variable on the UI that lets
the user know the install size of the MSI. I see the property InstallSize
for the MsiPackage Element definition. Can this value be queried from an
existing MSI?
33 matches
Mail list logo
