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 have a standard Visual Studio (2008) application setup project, which generates an msi containing a few files. I noticed however that: 1) When the msi installs and some of the files already exist, it simply silently ignores these files. This is the behaviour that I don’t want, because of obvious reasons. 2) When I uninstall the msi, it doesn’t delete my main dll file.
How can I fix these two things? Together they make it impossible to automatically upgrade my software.
I had the exact same problem and eventually gave up. Getting it to work is a horrible, complicated process involving lots of GUIDs. You’ll feel very dirty afterward (assuming you ever get it to work).
My advice is to switch to Inno Setup which is much more suited to people like you and me.
Leave .msi to people who do ‘corporate rollouts’ instead of ‘installs’.