Installation software
Once you have coded your software, you will often have a number of files that the main EXE file is dependent upon (dependencies). Such files may include DLLs, OCX files and font files. When distributing your program to other users, it is important to also distribute the dependencies. If you do not do this, the program may fail to run on other machines. Further, it is often important to make sure that your application is able to find the dependencies and sometimes, these extra files may need to be registered onto the user’s computer (e.g. a font file needs to be installed before it can be used).
In order to do all of the above, you will need to make what is called an ‘installation program’ for your software.
What are the other advantages of making an installation program?
- It will be easier for the user to download a single instillation file
- The installation software will ease the process of setting up the software and the files required by your program onto the users machine
- It will be easy for the software to remove itself from the users machine
- It looks professional and is expected by most software users.
- It will be easier for you to publicize (as we shall see much later!)
The fundamental point is that you should always make an instillation software even if it’s only one file you are deploying. This will make it easy for the user to get started.
Creation of an installation file is both free and more importantly, easy. But before you even consider creating one, you need to have basic things about your software sorted out:
- Is your software bug proof?
- Have you identified all the files your software needs – e.g. dlls, settings files, images, references and dependencies. Please note that files that may be installed on your system may not be on your users system.
- Have you prepared help files and license information if they are relevant?
- Have you decided whether your software will be free or not and have you programmed your software accordingly with all the relevant information in the help file?
With regards to point 2, how can you make sure you have identified the relevant files?
Are there any DLL calls that your application makes. If this is the case, then is it a standard Windows DLL? If it’s a standard Windows DLL then you may not need to include it on your instillation program; if not, it should be included.
- Identify all the other files that are used by your program (e.g. pictures, texts, sounds)
- Once you have identified all the files you think are needed for your software, simply compile your application
- Once the application is compiled, copy all the needed files and put it into a separate machine so that you can test to see whether it runs or not. If it does not run, make note of what files are missing from the errors you encounter. Then test by including the file that was missing.
- If you do not have a separate machine, consider setting up dual booting so that you can have one operating system dedicated to testing the application and one dedicated to programming only.
Once you have identified all the files needed, you are ready to proceed to the next section!
