application

In the Package editor under advanced tab, you can see the Manifest file tab which has been introduced in App-V 5.1. This doesn't exist in earlier versions of App-V. Using this tab, you can export or import the AppxManifest.xml file. Earlier if we want to do any custom changes we have to edit the deploymentconfig or userconfig.xml file(for adding scripts, editing FTA's etc). App-V 5.1 provides advanced way to edit those changes within the AppxManifest.xml. To do so, click on export as highlighted below in the Manifest file tab. This will export the AppxManifest.xml file to the local machine. choose the destination and click on save. Open the exported AppxManifest.xml using AppVManifestEditor. You can download the tool from here AVME AVME is a simple yet powerful tool to edit the AppxManifest file.My recommendation is not to edit the AppxManifest file manually. After opening the file using AVME,you can select the checkbox on left hand side to enable the type of script you want(Ma

Recently I came across a question in TechNet about App-V 5.0 Sequencer getting crashed when saving a package and its possible reasons. In this blog I am listing out the possible reasons for sequencer crash and its solutions provided from other App-V techies. First and foremost it's always  a good start to check in the event log when ever there is an issue. Check the screenshot as where to look for sequencer log entries. Always enable show analytic and debug logs from view menu. 1. rels files: The App-V 5.0 sequencer fails to sequence if there is any .rels files present in the package. You can identify a relationship part by the presence of a file with a ".rels" file extension in a folder named "_rels". To know more check the link from Microsoft. https://support.microsoft.com/en-us/kb/2843030 2. Invalid manifest detected: Missing or invalid ProgId entries might also cause sequencer to crash with Invalid manifest detected error log. Check the link from Dan Gough.