Raynet releases RayPack 1.3!
Raynet announces the release of the newest version of its packaging solution, RayPack 1.3
In the latest release of RayPack 1.3 there are a number of new features and functionalities that appear as a result of our customer’s needs. Raynet stays true to its core beliefs of developing products with in-house ideas and know-how, but to also focus on the desires and needs of the customers, both current and future, who need and use the product on a daily basis. Additional information and documentation for the new release of RayPack 1.3 can be found at: RayPack Release Notes
Here is a highlighted summary of the new features from RayPack 1.3:
- RayPack Support for App-V 4.6 packages
With this release, RayPack further extends its virtualization support reach, by joining support for App-V 4.6 along with the already supported Symantec Workspace Virtualization (SWV) and Microsoft App-V 5.0 formats. Numerous customers have not yet switched App-V 5.0 and implementation is still needed. Understanding that need, Raynet has ensured that users can prepare their packaging projects with the substantial feature set of RayPack’s PackDesigner and/or PackRecorder, and simply export to App-V 4.6; clean, simple and with minimal effort. The combination of RayPack’s broad set of valuable package content manipulation and evaluation options is a simple yet powerful way of going virtual, and now it is also available for App-V 4.6 SP2.
- Generation of Windows Installer Patch (MSP)
As an extension to the existing functionality of transform generation, any Windows Installer database (.msi) can be used as foundation for building MSP files. In RayPack 1.3, creating industry-standard format patches is straightforward and requires almost no technical knowledge. A patch can be created from two MSI files, or from quick adjustments made in the current session against the original installer database. It is a great way of deploying both small and minor upgrades, as well as, fixes to custom made, already deployed packages. Replacing a file with a newer version has also become a straightforward task with RayPack 1.3 – simply right click on a file to be replaced and select the new version. The file will then be updated on save/rebuild, keeping the original structure of files, components and other connections intact.
These are just two examples from many substantial improvements that Raynet has added to its packaging solution, showing its commitment to the product roadmap. Other features are, for example, an extended features management for the user interface, COM extraction and self-registration, and run-time files and folder operations.
Additional information can be found on our website www.raypack.net
Download the relesase notes: RayPack Release Notes
Raynet GmbH is a leading and innovative service and solution provider in information technology and specialized in the architecture, implementation and operation of all tasks within "Application Lifecycle Management". Raynet's Headquarters is in Paderborn, Germany and has additional locations throughout the region as well as locations in the USA, Poland, the UK and Belgium.
For over 15 years, Raynet has supported hundreds of customers and partners with its products and solutions for enterprise application management projects worldwide. These include license management, software packaging, software deployment, migrations, client engineering and much more. Additionally, Raynet maintains and cultivates strong partnerships with leading companies in Application Lifecycle Management.
Raynet products and solutions are unique in design and functionality. Their development is highly driven by our customers and partners who play a big role in the development of our products and are a key reason why our products are always cutting edge. Whether you want to introduce a new deployment tool or to start a SAM project, whether you want to plan a packaging factory or do a migration - Raynet is the choice for best-of-breed-practices in services, products, and solutions for Application Lifecycle Management.
Press releases you might also be interested in
Weitere Informationen zum Thema "Software":
Warum „Minimum Viable Cloud“ ein Schreckgespenst ist
Etwa vor einem Jahr hörte ich im Rahmen einer Projektbesprechung erstmals das schreckliche Akronym „MVC“. Mein Kontakt nannte diese Abkürzung wieder und wieder und ich wusste nicht, was sie bedeutete. Zunächst tippte ich auf „Model-View-Controller“, bis ich lernte, dass MVC für „Minimum Viable Cloud“ steht. Der Begriff leitet sich von „Minimum Viable Product“, kurz MVP ab, wörtlich ein "minimal überlebensfähiges Produkt“.Weiterlesen