The only versions I have seen released are 2.0, 3.0, 3.5, and the Beta of 3.6.
1) DifxApi I don't see Difx in 2.0 (I thought it was in there, it may be, I'm just not seeing it, but 2.0 is quite old and not supported any longer). The version in 3.0 and the later 3.x releases is different, there was a discussion about some of the differences at the time it was updated (would have been about a year ago if memory serves). 2) WYSIWYG WiX/Votive doesn't have WYSIWYG for MSI dialog creation. There are some third parties that have done this. IIRC, Rob M blogged about some of them a couple of times (search his blog for WYSIWYG). I'm sure the team would appreciate one contributed if anyone is ambitious enough to write one. There are enough deficiencies in Windows Installer's GUI that I usually recommend either external UI via bootstrapers (such as Burn) or embedded UI (which has other deficiencies) as workarounds. 3) Orca validation "Full MSI Validation Suite" is the highest degree of validation for MSI files. The "Logo" validation suites are subsets of "Full". Also, AFAIK the latest version of Orca is 5.0.7069.0 from Windows SDK 7.1. 4) SelectionTree The feature selection tree is part of Windows Installer/MSI and that behavior is not customizable. 5) Errors in MSI logs Errors surface in MSI logs at the point where you find the translated equivalent of "Return value 3". From that point, backtrack in the log up to the cause of the error. (http://msdn.microsoft.com/library/windows/desktop/aa369778.aspx) 6) Mutually exclusive (opposite) conditions My best advice is a pattern: <?define MyEnableCondition="((VersionNT = 501 And ServicePackLevel >= 2) Or (VersionNT = 502 And ServicePackLevel >= 1) Or (VersionNT >= 600)) And Not EXISTINGPRODUCTS"?> <Control ...> <Condition Action="enable">$(var.MyEnableCondition)</Condition> <Condition Action="disable">NOT ($(var.MyEnableCondition))</Condition> </Control> 7) Stable release Right now 3.5 was RTM about 9 months ago, and 3.6 was declared Beta almost a month ago. Your welcome, Blair -----Original Message----- From: Calin Iaru [mailto:ca...@dolphinics.no] Sent: Thursday, November 17, 2011 3:11 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] questions about upgrading to a stable wix version Hi, We’ve been compiling with 2.4 for a long time we are considering upgrading to the latest 3.6 version. I would appreciate if you could answer these questions: 1) 3.6 plays nice with DifxApi. The SW stack contains drivers that have to be installed and upgraded. I have custom actions that are triggered before and after installing drivers and everything has to be smooth. Ideally, it should offer the possibility to Force Repair when installing the drivers, something that 2.4 cannot. 2) 3.6 comes with a graphical editor for dialogs. I would like a WYSIWYG editor that can generate the proper WXS syntax. With 2.4, I use a bitmap as a white background and then have to cut it around checkboxes. 3) This q is not related to WIX, only to MSI: I am using Orca to validate the database. I looked at the version – the file is as recent as 2009 - and I would like to know if there are new ICEs or cub files that can be executed against the MSI. The highest validation is for Windows Vista Logo – is this the most severe level? 4) The SelectionTree control looks legacy. I would like an ST that just checks and unchecks without asking “Install from Source”, “Always install from Source” from a drop-down menu. 5) Sometimes, the logs taken after installing MSI /l*xv log.txt contain error messages like this: SELECT `Message` FROM `Error` WHERE `Error` = 1707 However, the precise source is not known. I would like a stack or a more granular context around this error. And some errors can be ignored because the installation does not fail. Regarding the request for a richer context around error messages, I expect that this is a feature offered by the OS. If 3.6 can do anything about it, then even better! 6) Certain conditions need both the true and false cases. I would like to have only the true case specified, and WIX generate the rest for me. <Control Id="Back" Type="PushButton" X="180" Y="243" Width="56" Height="17" Text="[ButtonText_Back]"> <Condition Action="enable"> <![CDATA[((VersionNT = 501 And ServicePackLevel >= 2) Or (VersionNT = 502 And ServicePackLevel >= 1) Or (VersionNT >= 600)) And Not EXISTINGPRODUCTS]]> </Condition> <Condition Action="disable"> <![CDATA[Not (((VersionNT = 501 And ServicePackLevel >= 2) Or (VersionNT = 502 And ServicePackLevel >= 1) Or (VersionNT >= 600)) And Not EXISTINGPRODUCTS)]]> </Condition> <Publish Event="NewDialog" Value="FirewallDlg">1</Publish> </Control> 7) What is the most stable version and when is the next stable version scheduled for release? I assume that there are no problems writing WIX code and compiling MSIs for XP to 7. Thank you for taking the time to answer these questions. Calin ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
