As soon as a capture project (RCP) has been opened for edition in PackRecorder, it is always possible to build a target package from it.
Always means, that from a technical perspective, the Build option is permanently available. Users may simply use the hot key F7 to call the Build dialog at any time during a PackRecorder working session. From a logical point of view, packages should not be build from invalid or incomplete resource bundles. Therefore, it is highly recommended to review and adjust project contents first, and only build target packages from them when the interface of the PackRecorder Editor provided sufficient options to ensure that the target package will be fully productive.
In fact, it is recommended to build RPP (RayPack Packaging Project) files first, which may be edited and validated within the substantial PackDesigner Editor interface, before actual target package formats, such as MSI's, are built.
However, from an RCP project opened within PackRecorder, packagers may build the following target formats:
•RPP
•MSI
•App-V 4.6*
•App-V 5.0*
•ThinApp**
•SWV***
•MSIX
•MSIX app attach (VHD)
•Citrix AppLayering (LAYPKG)
•Intune (win32 package)
_________________________________
* Only when the virtualization pack has been licensed
** Only when the virtualization pack has been licensed, and the ThinApp SDK is installed on the packaging machine. Please refer to the Release Notes for details regarding supported ThinApp SDK versions
*** Only when the virtualization pack has been licensed, and the SWV agent is installed on the packaging machine. Please refer to the Release Notes for details regarding supported SWV agent versions
|
Be aware: Building is a different process than simply saving. When a target package is build, all resources are checked for validity and existence, all target format restrictions are evaluated, and finally, the target package files (e. g. *.msi and *.cab files) are newly generated.
Saving changes made to a file does not include all these steps, but simply saves the updated state of the current project. |
|
WARNING Building means to determine the target architecture as well. It is not recommended to switch the architecture as part of the transition between RCP and any target package or project type. Doing so may cause issues, since the recorded snapshots base upon changes that affected the original system in its current architecture state (either 32-bit or 64-bit).
Essential modifications that are only present for another system architecture will most likely not be available within the RCP, and therefore missing in any exported format if the target architecture is switched.
RayPack allows users to perform this type of configuration switch, but it is highly recommended to double-check the requirement to do so, and triple-check the usability of the generated target file. |
To Build a Target Package
1.Click on the FILE button within the Main Toolbar at the top of the PackRecorder Editor application screen, or simply hit F7 on the keyboard.
oThe same result is achieved by pressing the Build package... button on the bottom of the screen.
2.Select Build from the options menu column on the left-hand side
Make sure the radio button To disk is selected.
3.Decide whether the newly created target format object should be displayed in the context of a system explorer instance once the build process has finished. If such an inspection explorer is wanted, users have to activate the checkbox Open the folder after the building is finished, displayed within the Settings section, at the lower dialog area.
4.Click on the tile that represents the desired target format (see the list of available target formats above)
5.Define the target package name and location
6.Click save
7.Wait for the process to finish.
Depending on the complexity of the resources that have to be molded into the target package format, the build process may take a while. Please note the process information displayed within the progress dialog: The currently processed resource is displayed by type and path, indicating the area of activity and possible reasons for longer waiting periods (e. g. because a file that has to be deployed with the package is quite large).
To Build a Target Package and Save It to RayFlow
Chapter Saving files in RayFlow describes how to build a package and upload it automatically to the current RayFlow instance.