hing approach).
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Thursday, September 06, 2012 1:48 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn: WixStdBA and MajorUpgrade
But the UpgradeCode's are identical, and burn isn
do nothing approach?
Thanks,
Jacob
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Thursday, September 06, 2012 1:31 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn: WixStdBA and MajorUpgrade
Sounds very much
ing it to think it doesn't need to install the newer MSI.
>
>
> -Original Message-
> From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
> Sent: Thursday, September 06, 2012 11:52 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX
n for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn: WixStdBA and MajorUpgrade
I'm going to reset the VM and try this again, as I feel I must be missing
something simple. (The logs would make sense if it's logging once per
element.) The behavior
ssage-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Thursday, September 06, 2012 11:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn: WixStdBA and MajorUpgrade
What does your Upgrade table look like?
On Thu, Sep 6, 2012 at 7:40 AM, Hoov
What does your Upgrade table look like?
On Thu, Sep 6, 2012 at 7:40 AM, Hoover, Jacob wrote:
> So I'm finally getting back to burn and I am running into a bit of
> confusion. Prior versions of my application were installed with
> DotNetBootstrapper as burn was still in its infancy. Now that 3.6
So I'm finally getting back to burn and I am running into a bit of confusion.
Prior versions of my application were installed with DotNetBootstrapper as burn
was still in its infancy. Now that 3.6 is official, I wanted to again look at
burn and see if I could get a single polished UX. On a VM
7 matches
Mail list logo
