Add true App-V support for your own products
While some of the files in both old and new App-V packages are plain-text XML files, the most crucial main package file (.SFT file in legacy App-V, .APPV in the new one) is in the binary format that has a complicated structure to parse and encode. Implementing a complete and reliable support for both reading and writing this file format involves a lot of development effort using lacking, scarce and non-existent documentation. And without the main package file there is only so much your software can do by fiddling with the XML files. Because of this any software developer looking to add full and complete support for App-V packages in products such as package inspection tools, editors, packaging tools etc. will have instant benefit from being able to "drop-in" this functionality without lengthy development time and process. As a bonus, Lib-V also includes support for those plain-text files as well, removing the need to battle with several different flavours of XML and inter-dependencies between files.

Create in-house builder of App-V package
With Lib-V, software vendors can make their own custom packaging tool to use in the build process to output completely customized App-V packages of their own software alongside the traditional installer. This package can then be distributed as an additional method of software delivery for those customers who have App-V infrastructure in place and would otherwise require re-packaging of the original product installer. Unlike using Microsoft's supplied Sequencer, Lib-V offers raw access to App-V package files and the possibility to affect every possible bit of information inside those package files, all without difficult-to-automate and difficult-to-integrate build processes as compared to using native tools.

Enhance your App-V related services
If you are an organisation providing consultancy over App-V, you could differentiate yourself from the competitors by having the most comprehensive custom-built toolkit in packaging services. For any consultant/developer having experience with .NET language (and since App-V 5 has a strong reliance on PowerShell, you most likely already know the basics of .NET) it's easy to start doing interesting things with Lib-V by building front-ends and tools.

Lib-V offers the following features:

App-V packages up to 4.6 (incl. SP2)

• Decodes all known SFT file versions
• Deserializes all known OSD, SPRJ, XML Manifest and App-V package MSI file versions
• Encodes all known SFT file versions
• Serializes OSD, SPRJ, XML Manifest and App-V package MSI files
• Comprehensive encoding control over package parameters
• Access to SFT package's internal data and its virtual environment
  • Internal directory structure
  • Virtual Registry (VREG)
  • Virtual Filesystem (VFS) mappings
  • Virtual Services
  • Virtual Fonts
  • Directory entry ACLs
  • Other internal attributes and data
• Access to OSD, SPRJ, XML Manifest and App-V package MSI's properties and elements in object-oriented fashion

App-V packages 5.0 and up (incl. SP2)

• Decodes all known APPV file versions
• Deserializes all known Dynamic User and Deployment Configuration files
• Encodes all known APPV file versions
• Serializes Dynamic User and Deployment Configuration files
• Access to APPV package's internal data and its virtual environment
  • Internal directory structure
  • Virtual Registry (VREG)
  • Virtual Filesystem (VFS)
  • All Integration Subsystems and Application Extensions
  • Other internal attributes and data
• Access Dynamic Configuration Files' properties and elements in object-oriented fashion