Experts in enterprise software deployments agree that you will most likely run into a scenario that requires a wrapper.
A wrapper is a piece of software that sits between your software distribution and your setup program. Instead of calling the setup program in your package, the software distribution calls the wrapper and the wrapper in turn calls the actual setup. In that sense, PackageShell is a wrapper.
Wrappers have developed a bad reputation because they can potentially disturb the communication that should occur between the setup and the software distribution system. If a setup program gives a feedback because it encounters an error, the software distribution systems needs to know about this - if the wrapper was poorly designed, that feedback might be lost.
PackageShell is well aware of all standard procedures programs should use to communicate status back to the calling system. It makes sure all available parameters are used to leverage this information. The mechanics typically include
- MIF status files
- return codes
- Windows installer logs
- standard error/output logs
With PackageShell you make sure that you're using recommended procedures to detect and report errors. The built-in intelligent reporting of errors will make troubleshooting a lot easier than before.