Migrating to install4j 12
In most cases, migrating to install4j 12 usually just involves opening and saving your project with the install4j 12 IDE. Nevertheless, there are some considerations with respect to backward compatibility and some behavioral changes.
Migrating to install4j 11
In most cases, migrating to install4j 11 usually just involves opening and saving your project with the install4j 11 IDE. Nevertheless, there are some considerations with respect to backward compatibility and some behavioral changes.
Migrating to install4j 10
In nearly all cases, migrating to install4j 10 usually just involves opening and saving your project with the install4j 10 IDE. Nevertheless, there are some considerations with respect to backward compatibility and some behavioral changes.
Migrating to install4j 9
In nearly all cases, migrating to install4j 9 usually just involves opening and saving your project with the install4j 9 IDE. Nevertheless, there are some considerations with respect to backward compatibility and some behavioral changes.
Migrating to install4j 8
In nearly all cases, migrating to install4j 8 usually just involves opening and saving your project with the install4j 8 IDE. Nevertheless, there are some considerations with respect to backward compatibility and some behavioral changes.
Migrating to install4j 7
In nearly all cases, migrating to install4j 7 usually just involves opening and saving your project with the install4j 7 IDE. Nevertheless, there are some considerations with respect to backward compatibility and some behavioral changes.
Migrating to install4j 6
In nearly all cases, migrating to install4j 6 usually just involves opening and saving your project with the install4j 6 IDE. Nevertheless, there are some considerations with respect to backward compatibility and some behavioral changes.
Migrating to install4j 5.1
The following new features in the install4j 5.1 require consideration when migrating from 5.0:
Migrating to install4j 5
Those who made the move from install4j 3 to install4j 4 will remember that it was a lot of work to migrate custom code, because most core concepts had been changed.Not so with install4j 5 : Your old project file will be transformed to the new format and most projects will work right away, without the need for any manual work. If you are interested in the changes in the project file structure, please see the file
config/transforms/transform_3.xsl
in your install4j installation directory.