If you change the version (manually or via a auto increment), AND you change the Product Code (which is what Product Id="*" does) then you will be able to do the Major Upgrade. In my prior post I was responding to this comment:
"That is ok, but then when I rebuild the installer (without any change, just rebuild) and run it again, it shows the new installation option instead of the repair one or when I increase the version, the upgrade one. " So when you did this because the Product Id="*" Version="1.3.1", and you indicated that you did not change anything, but just rebuild it, the result is that ProductCode was changed by WiX, but version was not, which would not qualify as a Major Upgrade, as you observed. Rather you have a new Product Code meaning a different product of the same version. I am relatively new also, but others have advised that implementing a MajorUpgrade is the simplest and generally recommended deployment plan. So to do this you either need to remember to change both the ProductCode (and ProductId = "*" lets Wix do this for you) AND you must change the version. (In an MSI only the first three parts of the version matter but in the bundle.exe all four parts of the version matter.) So for my project to always do a MajorUpgrade I use the ProductId = "*" and implement a auto versioning which increments for every build. Before I incremented the auto version I had the same behavior that you reported which confused my testing as I tried to understand what was happening. Also there is a concept of a Major Upgrade for the MSI and also for the Bundle.exe, so this issue needs to be addressed in both places. Originally I used Neil's bal:autoversion solution and then later I figured out how to write MSBUILD Tasks and implemented something that is more specific to my company's requirements. There are good reasons to do other forms of deployment besides MajorUpgrade, but I do not have any experience working with those approaches. I understand that if you do any of them you need to pay attention to the special rules that make them more complicated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-installer-upgrade-does-not-work-tp7589150p7589185.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
