Microsoft App-V application could not be started if manifest file in package contained entry "TargetInPackage=False"

Version 1


    Consider the following scenario.

    - The manifest file in a Microsoft App-V5 package contained the value TargetInPackage=False
    - The Target application was in the Microsoft App-V5 package
    - At Composition > Applications, the Microsoft App-V5 package was imported

    In this scenario, in a user session, the application could not always be started.

    The parameters field in the Microsoft App-V5 application managed application contains the following:

    value /appvve:adf21885-0936-4a1a-9eea-6dfceba37ec8_%APPVPACKAGECURRENTVERSION% but should be empty.

    The Command line should look like:




    The Microsoft App-V5 manifest file content "TargetInPackage=False" is not correct.

    The Microsoft App-V5 manifest file contains "TargetInPackage=False".

    When importing the Microsoft App-V5 package *.APPV we interpreter the content of the manifest file.

    With "TargetInPackage=False" we assume the selected application is outside the package.
    Therefore, the parameters field in the Microsoft App-V5 application managed application contains for example the value /appvve:adf21885-0936-4a1a-9eea-6dfceba37ec8_%APPVPACKAGECURRENTVERSION%.

    Sometimes this is not correct.

    The package can contain the application even with "TargetInPackage=False".

    When the application is inside the package, during the selection of the *.APPV package, the Command line should contain the Microsoft App-V5 path and program and no /appvve should be created.



    This issue is resolved in RES Workspace Manager 2014 SR3.

    In case the Service Release is not (yet) available or in case the Service Release cannot be installed, a revision containing this update is available on request at RES Support.

    IMPORTANT: A revision contains multiple fixes. Only apply this revision when you are experiencing a specific problem. Unless you are severely impacted by this specific problem, RES Software recommends that you wait for the next service release containing these fixes.