Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am wondering about the need for an install wizard for my little Windows Forms application. No database access, just file access on a shared network drive.
I have seen times when an executable is sent in an email, copied to a desktop and used.
Other times when an ‘install wizard’ seems to be used to set up the application.
What dictates the need for this or not?
And if I want to use one – what needs to be added to my windows form app?
If your application is truly just an .exe file, it’s probably okay to distribute it as-is without an installer. This might be preferable for more advanced users, because they won’t have to worry about cleaning up a broken/unwanted install – they can just delete the file and be done with it.
On the other hand, most Windows users are used to working with installers, and having shortcuts automatically created on the desktop or Start->Programs. This is where an .msi can really help. Also, using an installer will usually put your application in the “Add or Remove Programs” control panel, which most people know how to use. Also, if your application is more than just a single .exe file (e.g. multiple .dlls and resource files), you’ll probably want to use an .msi.
Creating an installer is easy, look at “Setup Projects” in Visual Studio.