RayPack 5.0 supports automatic conversion from MSI / RPP / MST files and repackaging from legacy apps for the following App-V formats:
•App-V 4.6
•App-V 5.0 (+SP2, SP2 Hotfix4 and SP3)
•App-V 5.1
•App-V for Windows 10 (versions 1607 and 1703)
The following table summaries most important functional differences between different versions that RayPack supports:
App-V 4.6 |
App-V 5.X up to 5.0 SP2 |
App-V 5.0 SP2 and newer |
App-V for Windows 10 |
|
|---|---|---|---|---|
Shortcuts |
 |
|
|
|
Files |
|
|
|
|
Registries |
|
|
|
|
Extensions |
 not supported |
|
|
|
ProgID |
not supported |
|
|
|
Verb |
not supported |
|
|
|
MIME |
not supported |
|
|
|
EnvironmentVariables |
|
|
|
|
Shell Extensions |
not supported |
not supported |
|
|
COM |
not supported |
|
|
|
Services |
not supported |
|
|
|
Fonts |
not supported |
|
|
|
Application Paths |
not supported |
|
|
|
URL Protocol handlers |
not supported |
|
|
|
In order to get an App-V 4.6 / 5.X package, the following two scenarios are supported.
For simple applications already available in MSI format
Simple applications relying on native features and not on Custom Actions projects may be converted directly to App-V format. This method is fast and reliable and does not require usage of virtual machines. For more information about App-V conversion, refer to the Building packages chapter.
For complex applications already available in MSI format and legacy applications
Legacy projects must also be repackaged first. Complex MSI applications that rely on custom actions may not always be fully working after the conversion process. In this case, perform repackaging first to make sure the installation logic is expanded into simple entities (files, registries etc.) using the Repackaging Wizard or PackBot. After that, convert the repackaged output into the selected virtual format.