Hello,
I have a project that is in beta, soon to be in production release. There is a setup wizard for the project, At launch, my program reaches out to the server, and checks an XML file to see what version is the latest one on the server. Once it is determined (based on the assembly version compared to that file) that an update is required, it runs it's setup file, and exits.
The user should then run their setup wizard, it will re-install, and then when they re open it, they have the latest version.
I have the RemovePreviousVersions property of the setup wizard set to true, each release I am incrementing the assembly version and the file version, and the setup wizard's version, also updating the product code when it asks.
For some reason, several of my users are getting an unusual problem: When they install the new version, it's not there. It's the same version they had, but the assembly version on the exe's properties is the latest, but none of the coding changes had been passed across. It works for the install on my own machine, and for some of my users, but for some, it just fails to work correctly.
Going to add/remove programs, removing the application, and reinstalling it still did not work. I had to do that, and then ALSO go and delete the program files data (apparently the remove did not get rid of this folder?). After doing this, the reinstall finally worked. Has anyone ever dealt with something like this before, and do you have any clue how I can fix it?
Submit an article or tip