Jump to content

Safe Portable App-ing + Definition of Portable Program


Recommended Posts

Definition of Portable Program

In "short" ?, an application, launched, used and properly terminated, it can be defined "Stealth" only if it doesn't leave behind any entry, modified or created in the System to grant the application perfect functioning. This concept is valid for System registry and file System. It means, when a Portable application is terminated, System conditions must be restored to the state they were before launching the application. Any file, created, edited, or positioned in the file System, out of the Portable application's folder, they must be removed from the System and stored in the the application's folder. For files and folders, "move" function is mainly used for small volumes of data and "junctions" for big ones. Certain cases can be ignored as, for example, temporary files and some registry entries (MRU entries for dialog boxes, DirectX entries for DirectX-based applications, etc). To be defined "Fully Portable", a program must perfectly work on different PCs/Systems (if hardware and System are supported by the official application). Some optional components, add-ons and plug-ins can be embedded in the Portable application, to grant it properly functions in any condition. Also application settings and data must always be fully available in any condition. A perfectly working Portable application must not interfere with a possibly installed official version of the same application. Official local settings must be preserved and they must be available, for the installed version, when the Portable application is not in execution. Some applications are natively Portable (they usually doesn't modify the registry and the file System). The programs provided without an installer (eg, distributed in a compressed archive), not always can be defined Stealth and Fully Portable. The same concept is valid for programs folders, obtained unpacking the installers or obtained from installed applications. Many solutions and techniques are available to portabilize applications, leftovers and modifications can be managed by a Launcher (created, for example, using the PortableApps Format, NSIS, AutoIt, c#, a script/batch, etc). Otherwise, the application can be isolated through a virtualization tool (eg, Turbo Studio, ThinApp, Cameyo, etc). Some applications do not need any intervention but they are modified to be perfectly managed by suites (PortableApps Format, SyMenu, etc).

  • Like 3
Link to comment

Please sign in to comment

You will be able to leave a comment after signing in

Sign In Now
  • Create New...