dependencies for your executable program
There are many strategies to identify the dependencies for your project. You can use a tool like Depends.exe that ships with Visual Studio to identify dependencies on DLLs. If your application is made using Visual Basic then you can use the ‘Package and deployment wizard’ to generate a list of dependencies for you. Sometimes you will have to use your experience to identify the technologies you have used and the files you need to run it. This is especially true when you use a lot of third party components that may in turn use other components themselves.
depends.exe
Wow, my application depends on all those files? Which ones do I need to redistribute with my application?
For starters, there are certain modules you should never redistribute with your application, such as kernel32.dll, user32.dll, and gdi32.dll. To see which files you are allowed to redistribute, you can look for a file named REDIST.TXT on your development computer. This file is included with development suites like Microsoft Visual C++ and Visual Basic. You can also look up "redistributable files" and "redist.txt" in the MSDN index for more information on what files to redistribute, how to redistribute them, how to check file versions, etc. Another site worth mentioning is the Microsoft DLL Help Database ([1]). This site has detailed version histories of DLLs, and lists what products were shipped with each version.
Create an Icon For Your VB Project
Save the image as a 32x32 png and use a free, open-source program called png2ico to convert the png image to an icon resource. png2ico is available at ftp.robotz.com and the syntax to use it:
png2ico outfile.ico infile1.png [infile2.png ...]