For files, the project file simply points to where the file is to be found. Environment variables are used to minimize file path differences between systems, but no files are actually contained in the shareable project file. It is registry entries that would normally be a concern when sharing such work. However no registry data is contained within the project file-- only pointers to values in the registry. When a project file is used to create an MSI, all the files and registry data are collected based on the contents of the local system.

When you create a snapshot with the AppDeploy Repackager, a project file is created and used as part of that process. At this point, all the file and registry entries specified in the project are known to exist on the local system (because that is where they were detected). If you have a project file and wish to build an MSI, you need simply install and configure the software as desired, then use the AppDeploy Repackager to build an MSI using a project file (forgoing the need to perform a snapshot).

So where are these project files files? Plans are underway for a user portal that will support the sharing of files along with community ratings and comments for each.