In this series of posts I am going to take you behind the scenes of how our packages integrate with our operating system in App-V 5.0. The most logical place to start is with the package itself and understanding what is output by our Sequencer. Let’s take this Paint.NET package and try to understand how it is made up. report.xml This file is carried over from our 4.6 SP1 days and contains diagnostic and advisory items around our sequenced package such as any warnings or errors encountered during sequencing or any files that have been excluded. <PackageName>_UserConfiguration.xml This file is for user specific changes that can be influenced at the time of publishing a package to a user. For example if we want to deploy a package with different shortcuts or a specific script to a certain group of users. <PackageName>_DeploymentConfiguration.xml Similar to the above however this file is for global changes that can be influenced at the time of publishing a p...