What's New in Gridmetric Lib-V

What's New in Gridmetric Lib-V 6.4.0

Enhancements and new features in this build:

  • Lib-V now supports App-v 5.1 RTM packages. Please note that these packages do not have functional or technical changes to the package structure itself, setting AppVFormatVersion as Version51 only generates a newer MSI wrapper file compared to 5.0 SP3 format.
  • Windows 10 (32-bit and 64-bit) can now be selected as the supported operating system version in 5.X packages, corresponding to new "WindowsClient_10.0_x86" and "WindowsClient_10.0_x64" supported elements in App-V 5.1.

Fixes in this build:

  • Package scripts in 5.X packages would in certain situation be saved with extraneous double-quote character, this in now fixed.
  • COM integration mode would lose customizations (reverting to isolated status) on package save if no actual virtual COM entries are present in the COM subsystem, this is now fixed and COM mode is preserved on all package saves.
  • Wait -element would be removed from package script if neither Timeout or RollbackOnError was specified for the synchonous script, this is now fixed.

What's New in Gridmetric Lib-V 6.3.0

Enhancements and new features in this build:

  • Lib-V now contains ChangeFormatVersion() method for changing package format version for open 5.0 packages.
  • New package creation method for 5.0 packages now takes additional parameter setting the package format version for the new package.

Changes in this build:

  • New 5.0 packages now default to 5.0 SP2 format version instead of 5.0 RTM.

Fixes in this build:

  • Certain characters could be left unencoded inside .APPV file resulting package that could not be added to the App-V Client, this is now fixed.
  • Extraneous { and } characters could be added to AppIds for 5.0 packages, this is now fixed.
  • Shortname generation for FilesystemMetadata.xml file entries contained multiple inaccuries, these are now all fixed.
  • Extraneous empty nodes could be generated for certain COM entries, this is now fixed.
  • Extraneous empty nodes could be generated for certain URL protocol entries, this is now fixed.