Raynet is about to release the next major version of their software packaging framework RayPack pretty soon. As the beta phase has already begun, there are some functional highlights you should really take a look at. This blog intends to provide insight on the most interesting extensions of the new release during the upcoming beta period.

Since the licenses provided for beta testing contain all new features, you will have to wait for the official release to get information about the actual edition classifications. However, there is such a load of innovations, that there should be a significant plus for each and every edition!

Row tracking

Thanks to the new feature of row tracking users can track both, direct (PK/FK relation, also respecting conditions) and indirect (formatted strings for files, folders, properties, components etc.) references between data objects from within the TABLES editor. To increase productivity, the tracking mechanism automatically updates all connected rows when editing a cell or removing a row. The auto-update can be turned on and off directly from the TABLES editor interface.

ISM/WSI import

Good things come to those who wait. This is absolutely true for the transition mechanism from ISM/WSI projects to RayPack’s RPP project format. Which has, by the way, undergone a massive redesign between 1.4 and 2.0. It seems like the 2.0 is the optimal version for a solution switch between the old world of AdminStudio and Wise to the new RayPack universe.

Setup Wrapping

The Beta has a built-in feature for the creation of setup wrappers directly from the PackDesigner component: In the build settings screen, a checkbox can be used to create a wrapper over the current project. Depending on the selection, it can be generated as either an .exe file or as a command line wrapper (.cmd) that can be used to install the package.

Prerequisite Handling

The new Prerequisites view provides an easy way to define critical dependencies of the currently edited project. RayPack 2.0 contains a predefined list of commonly used prerequisites.

At package build, CMD or EXE wrappers respect the settings in order to provide an easy and standalone entry point while installing all necessary components of the package. Prerequisites resources are shared and available within the PackPoint location.

Curious? Simply visit www.raypack.net to get your own trial version!

Topic for the next post: The brand new MSI UI Editor interface