Any respect-worth program should help user not to think «where it is and how to run it»; once your user has downloaded the software from the Internet (or bought it on a CD), he should be only few clicks away from having the program running.
In the simplest case, of course, you can say something like «just unpack the files and take them to any place you wish», but it prevents your program from the normal Windows users experience: Start menu icons, Desktop icons, and one-click removal when user is dissatisfied.
With complex programs, things get even worse: does your user have to register DLLs or place them to system folders, create special folders, update settings and paths?.. Definitely not! The program must be INSTALLED seamlessly, including the friendly questions for appropriate settings and thorough adjustment of the system. Setup Builder is the thing that wraps up your program into an installer the easy and programmer-friendly way.
Setup Builder allows you to define, which files are to be deployed, and even individual properties for any file (shortcuts, visibility during the installation process, compression method and so on). It also allows adding redistributables of many environments (like VB) just to installer body and importing full Visual Basic projects. When installing, Setup Builder can check files lock, install system DLLs and services, register objects, as well as create shortcuts and serve component selection dialogs. Under the hoods, Setup Builder provides you with powerful script, allowing you to tweak any installation procedure parameters, show additional windows and do many other things.
The Vision Thing Tech companies can't just have products. They have to have a vision. At IBM, it's "on-demand" computing. At companies in just about any business more complicated than hubcaps, it's "selling solutions." At EMC, the biggest player in data-storage hardware,