I chose a standard Windows Installer deployment because I thought it would match more closely with the needs of the typical Library system user. The Library application is meant to be a permanent feature on the target workstation, so it's likely that someone with IT knowledge or administrative privileges will perform the actual installation. As it is a licensed product, there is little chance that I would be putting copies of the Library installation out on my public web site. A CD distribution—common for MSI installations—is the expected medium. Also, since it's a quality piece of software from a trusted vendor (that's me), there isn't a need for a protective sandbox. Still, the application does include several files, including two online help files, so an
XCopy installation would be a burden. All in all, a standard MSI installation is the best deployment plan.
The Setup Wizard automatically adds my project assembly to the MSI file, but I am sure other files are needed to properly deploy the Library Project. A quick look through the previous chapters reveals the following list of file requirements:
This must be installed on the target system to run the Library application. The setup program will need to automatically install the framework if it isn't already on the target system.
This is the primary assembly. The install would be useless without it.
These online help files will be installed ...