Developers have to choose what and how to present to users, when they are developing software product. The most usual form of the software distribution on Windows operation systems is installation (or setup) program.
Technical features depend on the chosen installation software, your program features, other components and drivers necessity etc.
But some general paradigms can be highlighted. Let’s talk about this using our company’s TeamAlerts as example.

First of all look at the reviews and comparisons, estimate requirements and public opinion (list of the installation software).
For example, there is a common view that installer for products requiring administrative permissions for making changes in registry and system folders are better to create using Windows Installer (*.msi). Simple programs could be installed by the standard *.exe files.

If something could be changed in the Windows, it’ll be changed. For example, operating system could be installed not on the first disk’s partition whose letter could be anything than ”C”, Japanese locale could be default in the English system etc.
You may not expect the default options and settings. When you are using any folder, environment variable, registry key, driver, check that they are exist and available beforehand.
Always alert user before any renaming, moving, changing settings, especially if you do this with administrative permissions.

Don’t be lazy to check installer running on the several real irtual machines. Try to make test environment vary as much as possible. Use tests with highest possible coverage.

If user should answer some questions and choose some options, try to do anything for definite understanding what heshe should do and why.
The installer’s dialog boxes are split in zones, which are used for different purposes.

Figure 1 – Installation wizard’s zones

Figure 2 – Total progress bar and actions list

Besides, you can log the installation process. Traditionally the operating system Temp folder is used for this purpose but it is recommended to check location using the environment variables andor system API functions such as GetTempPath.

Installation software uses default images and icons in the installer. But it is more appropriate to use custom, product-specific artwork. Original splash screens, icons and logos leave a pleasant impression about the application and stay in user’s memory.

Figure 3 – Application-specific artwork

If installation has not succeeded, you have to suggest some solutions to user:
- Actions that user could do to resolve problem;
- The list of the problem’s causes;
- Support’s contact information.

Good uninstaller is an important part of the application. Program must be correctly removed in every case, even if your application has been tampered with (files deleted or settings removed manually).

Figure 4 – Uninstalling