Removepreviousversions already installed

Active Oldest Votes. I can assure that the version is using the Version syntax and it's been updated, example, from 1. UpgradeCode as well ProductCode are always updated automatically as well. UpgradeCode should remain the same, only ProductCode should change.

Also, since you are receiving the message you mentioned, you didn't increase the package ProductVersion and change the ProductCode. Where did you make the changes? I rectify that, ProductCode is the only one that changes. I use the Properties window in the Setup Project. You need to also increase the ProductVersion. The Assembly version number also needs to change for it to be replaced by the installer.

The solution is simply to right click on the setup project and click rebuild. Hope this help to future readers :. Stephane Rolland Anders M. You need to change the Assembly version in your projects as well — rageit. I struggled with this for a long time but it is very simple.

Keep the UpgradeCode variable in the properties window the same for different versions of the same product. Change your ProductCode variable between different builds. Anton Esterhuizen Anton Esterhuizen 21 1 1 bronze badge. Create a. HaibaraAi HaibaraAi 1 1 silver badge 11 11 bronze badges. Wednesday, May 13, PM. Hi David, This property can do what you're looking for. If you haven't already, add a setup project to the solution, then click the Setup project node in Solution Explorer.

The default value is False, just change it to True. If you have anything unclear, please feel free to tell me. Sincerely, Kira Qian Please mark the replies as answers if they help and unmark if they don't.

Friday, May 15, AM. So how will this work? With this set to 'true' I will then rebuild the project to create a new msi file. When i run setup to install this latest build, will i get an error or will i get a prompt that this program is already installed on my computer? Do i get the option to cancel or continue Is that how it will work?

Thanks Please remember to mark the replies as answers if they help and unmark them if they provide no help. Sign in to vote. Thank you - Karen Ahmad. Thursday, March 19, PM. Just me won't upgrade Everyone and vice versa. Phil Wilson. Friday, March 20, PM. Thanks for the reply! Therefore, the program is always installed for all users. I would appreciate any other help you can offer. Tuesday, March 24, PM. I believe this means that the installation defaults to "Install for everyone" and that the user is not able to change it.

That would mean that all the installations are installed with the same value. Please let me know if I am missing something here. After I made these modifications I installed v3. If so how would I do that? Thank You - Karen Ahmad. I am having a similar problem with the uninstall not occurring first sometimes. I have a rather simple installer that I made with visual studio that installs a couple EXEs and a DLL along with some other files into a directory.

When I need to do a new release, I update the Version field with a new version number in the installer and VS prompts me to update the product code, to which I answer YES. I have verified that it does indeed change the product code, but the package code also gets changed with it verified by diffing project files using sourcesafe. The UpgradeCode never changes between versions. My version number changes are of the form: "1. When I've done all that, I build the installer.

When I install the new version I always install for all users and always into the same directory , I have seen three different results at various times: 1. It will uninstall the old one first and then install the new one what it is supposed to do.

It is very frustrating to explain to users that to be safe, they have to uninstall the old manually before installing a new release because I have to tell them "it doesn't always uninstall the old one like it is supposed to".

Any suggestions? Why isn't this working? What am I missing here? Thursday, June 11, PM. There are some general rules about upgrades and some specific to Visual Studio versions 1. Old and new products must have identical UpgradeCode values and different ProductCode values.

Old and new products must have identical values for InstallAllUsers. New product's setup Version the setup project, nothing to do with file versions must be higher. All setup versions again, not file versions must be 1. Visual Studio RemovePreviousVersions is not the same as and uses file update rules. Therefore if you want to update files you must increase file versions.

This is normal practice in all setups, patches etc that file versions are updated if they have new content. Visual Studio RemovePreviousVersions behaves like an uninstall of the older one followed by an install of the new one, and rules still need following, but you could get away with not incrementing changed file versions because of the "uninstall then install" nature of the upgrade.

Thanks for the response. I was familiar with , but 5 and 6 I did not know about. So you're saying that only individual files whose 'file version' is different would be "uninstalled" replaced maybe is the better word when I do an installation over the top of an older version of the same thing. And it is a file-by-file decision made by the installer. Is that right? I'm assuming when you say "setup version" you're referring to the "Version" field in the installer deployment project properties window of the installer project.

I do increment that e. I'm not sure what exactly you mean by file versions, though. Only applications seem to have file versions as set in the Version field in the resource file and seen by right clicking an EXE file and viewing the version tab.

Things like DLLs and text files don't seem to have this information, so I don't think I know what a 'file version' is. Could you explain? Friday, June 12, PM. Yes, Visual Studio upgrades RemovePreviousVersions use file replacement rules, and yes it is a file by file decision made by the installer.

Yes, the setup project version is the Version in the deployment project's properties window. All binaries have versions, and that includes exe and Dll files. If your Dlls don't have a version then they should have. Data files don't have versions, correct, and data files don't get replaced if they have been updated. So if you install a database and then use RemovePreviousVersions it will not replace the installed database if it has been updated.