Thanks for the verification of the current behavior.
I have added a feature request:
http://sourceforge.net/p/wix/feature-requests/725/
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-Version-and-patching-tp7579655p7584964.html
Sent from t
wix-users@lists.sourceforge.net>
> Sent: Saturday, April 6, 2013 10:11 AM
> Subject: Re: [WiX-users] Bundle Version and patching
>
> That's a pretty scary hack to me. I could see us doing things in the future
> that totally get confused doing that. It seems like this would be a bett
ML toolset.
Sent: Saturday, April 6, 2013 10:11 AM
Subject: Re: [WiX-users] Bundle Version and patching
That's a pretty scary hack to me. I could see us doing things in the future
that totally get confused doing that. It seems like this would be a better
feature request for the engine to handl
That's a pretty scary hack to me. I could see us doing things in the future
that totally get confused doing that. It seems like this would be a better
feature request for the engine to handle. The behavior you are seeing right
now is completely expected but I can totally see why it'd be nice if pat
I had the same problem. What I did to solve it is in the product msi, I
created a custom action that runs on both install and uninstall to find the
bundle entry in Uninstall and update the DisplayVersion. When installing, I
create an OldDisplayVersion which has the version number for what is abou
Hi Christian,
I have run into exactly the same situation (the patching successfully
completed, but the ARP entry not being updated). Did you ever find a
solution to the problem?
Best regards,
Mattias
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.co
6 matches
Mail list logo
