Solved WiX v3 - votive problems

I now solved my wix v3 votive problems with newer builds of wix. The problem was that from a specific wix build on, the standard configuration was changed from any cpu to x86 and any cpu was not longer supported. I used my old .wixproj without change in newer version without discovering any problems.

When I changed to 3.0.4220.0, the TFS source control was not working any longer for the wix project itself but also causes the automatic checkout of items in other project types to not work.

After changing all any cpu references to x86 in my .wixproject everything worked fine.

It's really weird that this caused the TFS source control to not work correctly anymore.

Btw this is reproducable, so it's not just a hazard that it works now.

IzPack now supports InstallerRequirements

The current trunk version of IzPack now supports the so called installer requirements. This means that it's now possible to define requirements for being able to start the installation. E.g. if a certain user has to start the installer, this will be checked by using a UserCondition with an installer requirement. If the condition is not fulfilled, a message will be shown and the installer exits.

WiX v3 - votive problems

The newest weekly build of WiX v3 3.0.4220.0 causes some problems in Visual Studio 2008 if you're using the votive integration.
In my installation, votive reproducable causes problems with sourcecontrol integration. I'm using the TFS Client. After installing votive, automatic checkout while editing is not working anymore in any project. In the votive project itself, almost every button for TFS is disabled.

Hope the next version of WiX is better, as WiX is a fantastic installer generator for the windows world.

How to debug variables and conditions in IzPack

From IzPack 3.11 on, there's a built-in debugger for variables and conditions. The debugger is activated when the installer is called with -DTRACE=true as JVM option.

Ex.1:

java -DTRACE=true -jar myInstaller.jar

The debugger shows up as a panel in the east of the InstallerFrame or if the guiModifier showDebugWindow is set to true, it will show up as seperate window.

Ex.2:

<modifier value="true" key="showDebugWindow">

IzPack now has built-in conditions

IzPack now has built-in conditions which means, that there are some predefined conditions which can be used in the installer. These conditions are:

• izpack.windowsinstall


• izpack.linuxinstall


• izpack.solarisinstall


• izpack.macinstall

There's also a PackSelectionCondition for every pack. The Ids for these condition will be built up from the pack id or if not specified, the pack name. If there's a pack called Testpack with id test.pack, there will be a condition called izpack.selected.test.pack

IzPack 3.11.0-beta1 coming soon...

The next version of IzPack installer is coming soon. There will be a preview on November, 30th. This should be a feature complete version. The final version will be released after a documentation update.

See http://www.izpack.org/ for more information.

RuleEngine (conditions): new features in 3.11

• conditional expressions:
  use + (and), (or), \ (xor) or ! (not) in your conditionids:
  there are two conditions with ids cond1 and cond2.
  ex1. pack test can be installed if cond1 and cond2 are evaluated to true:
  
  ex2. pack test can be installed if cond1 or cond2 is evaluated to true:
  
  ex3. pack test can be installed if cond1 is evaluated to false:
  
• added support for conditions in jobs in ProcessPanel:
  ex1. ...
• fixed condition evaluation in PacksPanel

IzPack 3.10.1 released

Ein Service-Release des Java Freeware-Installer IzPack wurde veröffentlicht.