PEBundle allows for an executable`s (or DLL`s) dependencies to be physically or remotely bound to itself so that they need not be distributed or installed separately from the application. Using a high performance compression algorithm, PEBundle compresses all bound modules so that the host executable`s size grows as little as possible given the bound data. Of course, in the case of a bound URL, the size increase is negligible since the data is retrieved from a network resource.
The binding of URLs means that you need not distribute unnecessary modules that already exist on the client machine along with your installation package. When your executable is invoked, the PEBundle loader will determine if the r>
emotely bound modules need to be downloaded, and, if so, display a window indicating progress of the download to the client machine and subsequently place the module at the location you preconfigured it to be installed to then continue with normal execution of your application.
Some of PEBundle`s many uses:
Binding of URLs to an executable or module (DLL) so that file dependencies are downloaded only if necessary.
Compression and binding of modules to an executable or other module so that they need not be distributed along with the application.
Verification that the correct versions of runtime DLLs are installed on the client machine. No more DLL Hell.
Text can be inserted into the command line at runtime so a s cript can be bundled with its interpreter!
Inmemory bundling can sometimes successfully emulate a DLL so that it need not ever be extracted to disk.
Obfuscation of your executable helps protect it against tampering and cracking.
Can speed load time in some cases.
