1. Include an Uninstall: Make sure that you include an uninstaller with your software. Installers must include the ability to uninstall applications to meet Windows Logo requirements and is just a friendly thing to do. Making an uninstaller with Setup Factory is easy. Just select Uninstall > Settings from the menu and check the "Create uninstall" option. There are a lot of ways to customize and present your uninstall. See the User’s Guide and Help file for more details.

2. Write Out Your Application Information: It is a good idea to have your installer write out important paths and locations such as the application folder to the Registry or a settings file during installation. Doing this allows future installers, updaters and patches to quickly and easily determine where your application is installed without asking the user or searching the system. Here is a sample script that could be used to write out the application’s installation folder.  Usually you would put this in the "On Post Install" installation event (replace the Registry sub-key with your sepecific location):
Registry.SetValue(HKEY_CURRENT_USER,"Software\\Your Company Name\\Your Product Name","InstallFolder",SessionVar.Expand("%AppFolder%"),REG_SZ);
You can store any information you want, such as the shortcut folder used, the product version or anything else that might be important to your software.

3. Use Log Files: It is a good idea to have your installer create a log file during installation. This can be very helpful if a customer has trouble installing the software and you need to find out why. You can turn on and configure the installer’s log file by selecting Project > Log Files… from the menu. Setup Factory automatically writes out all of the detail that it can to the log file.  If you want to include your own custom information, use the SetupData.WriteToLogFile action.

4. Set Minimum System Requirements: If the software that you are installing has specific minimum system requirements to run properly, it is a good idea to check those requirements before starting to install files and modify the user’s system. You can configure most common system minimum checks by selecting Project > System Requirements from the menu. At the very least it is a good idea to leave the "User must have administrative priviledges" checked in most cases. If you need to do more in-depth system checking than the options allow, you can use actions and scripts to do so.

5. Marking Shared Files: If you are installing files that may be shared by other applications on the user’s system (such as ActiveX, DLL and OCX files) it is important to turn on file usage counts for those files. To do this, double click the filename on Setup Factory’s main screen. Go to the Advanced tab and turn on the "Shared/System File" option. This will ensure that the file’s usage count is incremented in the Registry and protects the file from being deleted by the uninstall if it is still being used by other applications.