Hello Everyone,
We are facing an issue during an upgrade of our Product on one of the user
machines.
1. While upgrading, a popup asking for the location to the previous
installer keeps showing up after which the upgrade fails.
2. Even after removing the previous version from the Add/Remove Programs
Hi,
My question is a simple one. How do I tell Wix not to shutdown other
applications during an upgrade?
I have an installer that installs Explorer shell handlers in addition to
the entire product. The burn bundle decides when to install 32 Vs 64 bit
MSI which each contain the handlers. Display in
ing different files between the two builds? I would ensure
> the common files are in one CAB and anything that is unique to x86 vs x64
> in their own CABS.
>
> -Original Message-----
> From: Ashish Agarwal [mailto:ash...@mangoapps.com]
> Sent: Friday, August 01, 2014 10:58 AM
14 at 9:12 PM, Hoover, Jacob
wrote:
> Yes, and because of this burn is including the appropriate CABS. Are you
> using the existing WiX build events to sign the MSI and CABS? I do believe
> the events are timed such that MSBuild isn't going to trigger a rebuild if
> CAB cac
27;s look in Orca?
> --
> John Merryweather Cooper
> Build & Install Engineer - ESA
> Jack Henry & Associates, Inc.(r)
> Shawnee Mission, KS 66227
> Office: 913-341-3434 x791011
> jocoo...@jackhenry.com
> www.jackhenry.com
>
>
Hi,
We are in the process of migrating to Wix from the old Visual Studio
installer and are hitting an issue.
We use a single setup project that runs once in 32 bit mode and once in 64
bit to generate two MSI files. These are then packaged together using Burn.
When the external cab files are not si
There is a Batch build option in visual studio.
On Jul 31, 2014 3:51 PM, "Berend Veldkamp" wrote:
> I know I have to create separate msi's for x86 and x64, and I managed to do
> so in Visual Studio. However, to build both versions, I need to manually
> switch the platform between x86 and x64, and
7 matches
Mail list logo
