kimmov wrote:Hmm. Just tried to build X64 MSI installer from folder I used for 2.13.10 experimental release (all files compiled) and it failed. Because it tried to find files from Build\x64-folder. Which of course doesn't exist.

I have currently no access to my developer machine and can't test it. You can define the x64 paths in the Config.wxi file:

Continuing this topic since now we are preparing 2.14. stable release (in "fast" continuation of 2.12 stable releases). And Tim submitted a patch to port WiX installer for 2.14 stable release.

My opinion is we must have only one installer for stable release (having more for experimental releases is fine, they are for testing anyway). How could users (and download services for that matter) decide which installer to use/offer if we had two of them?

So if we add WiX installer then we need to drop the InnoSetup installer. Code can stay in SVN but we don't release it.

We've had WiX installer available for some time now. And we've discussed about it in this very topic. But I'm not totally sure about the current status. What exactly is missing from WiX at the moment (compared to InnoSetup)? We definitely need to switch to WiX at some point, no question about that. But the question is if we are ready to do the switch now for 2.14 stable release?

No, I don't want to different installer types. They aren't compatible so we must have one clear release where we do the switch and cause all the trouble for the users. If we have two then some sites will offer one and some other. And since result is anyhow a bit different it will be a nightmare to debug possible problems!

I really doubt there will be new 2.x stable series after 2.14.x. Or well, with current pace of 3.x development maybe we need one...

The size problem is bad. There is one possibility to update release compiler to VS2010. I haven't yet installed full VS2010 but I probably have to do so soon. But then we would require WinXP Sp3 (Microsoft Visual C++ 2010 Redistributable Package (x86)). And that is a bit too drastic change now.

I've added the OpenCandy stuff to the InnoSetup installer now, and it may take several weeks for me to get it added to the msi installer.So that's one more reason to stay with InnoSetup for the 2.14.* release.

I do agree that long term we should switch to a msi based installer, to make it easy on administrators to roll out WinMerge to large quantities of machines.