BoxedApp Packer

BoxedApp Packer - a typical application consists of a whole set of files: data files, DLLs, ActiveXs, various frameworks like the .Net Runtime. Usually, to install such an application, an installer is created, which copies the files to the machine, modifies the registry and gets everything ready for the application to work correctly. But there are reasons when this method is not suitable:

• you need to create a portable application from a "regular" one and it is crazy or even impossible to rewrite the whole application (e.g. you have made a .net application);
• you do not want to tie up the client machine with additional files, such as a huge .net extension;
• the application should work right away! -- with no installation work required;
• the installer might not have enough permissions to install (ActiveX registrations are a typical example) and you want the application to work everywhere and with any level of user permissions;
• you want to hide the files you use: for example, third-party DLLs;
• you need to consider compatibility between different versions of components; for example, your application needs the 9-th flash and other programs need the 8-th or 10-th -- normally, the "last one to install is the right one" approach applies.

BoxedApp Packer is a solution that packages all dependencies into a single file that creates a virtual file system on startup (unpacking embedded files into it) and a virtual registry (including additional entries for ActiveX controls to work correctly). At that, the packed file won't create temporary files or modify the registry. Everything happens in memory. That's why neither a lack of rights to write to the registry, nor a lack of rights to write to the disk is a problem.