I have associated the Burn Version to the build system as at each build it will
have new version changing the last value 1.0.0.0 => 1.0.0.1To make the new
installer not to add anoter item to the ARP I have attached the event
PlanRelatedBundle and then I have set
e.State = RequestState.Absent;
to make related bundle uninstall even when the Burn package has a version that
differ for the last number.
But when I run the installer the second time (new build version with new
version) the installer interface is freezed and I can see multiple instaces of
the installer application on the process explorer of TaskManager, is it a bug
or could be a problem of my installation?I have seen this behavior even with a
simple sample that I have derived from the sample project posted here:
http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/
How can I make this working?
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
