Table of contents
TOC
Collapse the table of content
Expand the table of content

Virtual Application Package Additional Components

jamiejdt|Last Updated: 9/1/2016
|
1 Contributor

The App-V Sequencer has detected a directory that contains 64-bit and 32-bit executables and/or dynamic-link library (.dll) files that depend on the same side-by-side assembly. Typically, the Sequencer creates private side-by-side assemblies for all public assemblies that are used by the package; however, it is not possible to create 32-bit and 64-bit versions of the private assemblies in the same directory.

If the Sequencer detects a single conflict, it will perform the following actions:

  • Remove all of the existing 64-bit private assemblies in the entire package, whether or not the directory has a conflict.

  • Create only 32-bit versions of the private side-by-side assemblies.

You should natively install public versions of all the required 64-bit assemblies on the computer running the Sequencer and on all App-V client computers.

To locate the required existing public assemblies, open the directory where the package is saved and look in the VFS folder. For example, if the package root is Q:\MyApp, when you sequence the application, look in Q:\MyApp\VFS\CSIDL_Windows\WinSxS\Manifests and locate all of the existing public assemblies. The 64-bit versions of these files will always start with the following text at the beginning of the manifest name: amd64…. The exact name and version of the assembly can be found in the associated manifest file.

Use any of the following links to download and install the correct version of the required prerequisites:

© 2017 Microsoft