Okay, cool. I have a repro of this locally. It's a bug in Burn. Hope to
have fix in next build. Feel free to open a bug to track if you like.
On Thu, Oct 4, 2012 at 3:38 PM, Nick Ramirez wrote:
> Yes, targeting same MSI. The first patch changes an existing text file that
> got installed by the
Are the two patches targeting the same MSI?
On Sun, Sep 30, 2012 at 9:43 PM, Nick Ramirez wrote:
> The version I have is 3.6.3303.0. I took a stab in the dark and rearranged
> the elements various ways, but couldn't come up with a solution.
>
>
>
> --
> View this message in context:
> http://win
The version I have is 3.6.3303.0. I took a stab in the dark and rearranged
the elements various ways, but couldn't come up with a solution.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-failing-when-two-MspPackages-tp7580938p7580953.html
Sen
Hmm, could be a bug. I don't see anything in our tests that mimic that
exact behavior. What version of the WiX toolset are you using?
On Sun, Sep 30, 2012 at 12:40 PM, Nick Ramirez wrote:
> It seems that this only happens if I am installing two patches. If I
> comment
> one out and only have one
It seems that this only happens if I am installing two patches. If I comment
one out and only have one listed in the Chain, then it gets installed okay.
The log for a good attempt, only installing one patch shows:
Verified acquired payload: Patch2.msp at path: C:\ProgramData\Package
Cache\.unverif
5 matches
Mail list logo
