A typo. A simple typo mistake.
-Original Message-
From: Brian Lemke [mailto:brian.le...@apihealthcare.com]
Sent: Thursday, October 06, 2011 7:36 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action Fails when InsertingTemoporaryRows
view.Close();
...
with success. Note, I am recursively adding all files and folders from
my base folder to be removed.
Jacob
-Original Message-
From: Brian Lemke [mailto:brian.le...@apihealthcare.com]
Sent: Wednesday, October 05, 2011 9:48 AM
To: General discussion for Windows Ins
The scenario I am trying to handle is the cancel during uninstall. If I were
to just bomb the folder the rollback wouldn't work and it would delete the
folder anyway. I am going to try and see if I can pressure the team into
using 3.6. Don't know if it will be an issue or not. Initially t
.com
-Original Message-
From: Brian Lemke [mailto:brian.le...@apihealthcare.com]
Sent: Tuesday, October 04, 2011 2:45 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] C# Custom Action Fails when Inserting Temoporary Rows.
I'm hoping that someone can help me out. I canno
I'm hoping that someone can help me out. I cannot seem to figure out why my
custom action is constantly failing me. The action executes on uninstall and
is to browse the install folder and add files to the RemoveFile table (with a
few additional properties too) in the MSI so that the file is
I have a setup that installs as v1.0.0. Then I have a created a patch that
updates to v1.0.1 and second patch that will update either a v1.0.0 or v1.0.1
to v1.0.2. This works as expected. These are all minor upgrades (Product and
Upgrade Code stay the same with only changes to the product ve
Is there any way of creating a set of patches that are mutually exclusive? I
have software that has two patches A and B. Now If the software has patch A
installed it is to prevent install of B. I get this by sequencing A after B
and marking A to supersede B (now if you uninstall patch A it
Is it possible to prevent an update from applying to the system? I have a
scenario where I have shipped v1.0 of my setup which has patches 1 and 2.
After patch 2 is out but before the client can install it, they detect a
critical error in patch 1 that requires us to immediately patch it (cr
When building a Patch for a setup should a patch file contain all items that
could change or just the ones I know that have changed. For example I have
the following defined:
The two setups I have only differ by one file, say File1. Should
9 matches
Mail list logo
