Installer Removepreviousversions Doesn T Work

Does Not Contraction
Installer Removepreviousversions Doesn T Working
Doesn't Synonym
Youtube Full Screen Doesn T Work
Installer Remove Previous Versions Does Not Work

Active2 years, 1 month ago

How Do I Create The Setup Windows Service To Uninstall Then Install Service? See more: C#. Hi, i develop a windows service in C#. And my project has Installer, and Setup project. The setup project, installs service very well and it doesn't have any problem, but when i change project and create other setup, the new setup doesn't install new.
RemovePreviousVersions=True but previous version is not removed from the. Windows Installer doesn't allow cross. The same 'upgrades don't work. Visual Studio Installer Doesn’t Uninstall Previous Version – xombe. Description of the Problem: I’ve written a windows forms application that has a Visual Studio Setup & Deployment installer project.

C# discussions; Updated: 19 Jan 2019. 13,832,637 members. RemovePreviousVersions doesn’t work in VS 2008. Anderslundsgard 5-Feb-08 22:43. If I uninstall an then install it works fine but I don’t want my users to do that every time I release a new version.

I have a simple Web Setup project that reads from a Deployable Project.

Even though I have set the Setup to DetectNewerInstalledVersion to false I always get that annoying alert box that a previous installation exists and I need to go to the Control Panel and find the software to remove it...

Is there a way to add a script in a new new installation Dialog that could say A previous version was found, press NEXT to uninstall it. ?

balexandrebalexandre

54.4k34 gold badges209 silver badges303 bronze badges

4 Answers

In my case I found out that the setup project wasn't part of the configuration manager.Therefore, it wasn't rebuld on solution rebuilds and setup file with the new version and ProductCode wasn't generated.

The solution is simply to right click on the setup project and click rebuild.

Hope this help to future readers :)

Stephane Rolland

20.4k29 gold badges105 silver badges152 bronze badges

SimSimYSimSimY

2,6221 gold badge22 silver badges31 bronze badges

Does Not Contraction

Older versions are uninstalled automatically if you increase your Product Version and change the Package Code. This needs to be done each time you modify the setup project and build a new package.

If you keep the same version and Product Code, older builds cannot be uninstalled automatically. They are detected by Windows Installer before your new package is actually launched. So you need to uninstall them manually.

Cosmin PirvuCosmin Pirvu

19.6k5 gold badges35 silver badges56 bronze badges

The answer is not to use the Visual Studio setup project that's already integrated. I'm having the exact same problem: it won't remove previous versions even though I up the version, set it to remove previous version, check for previous version and rebuild, I can install but the files aren't updated. There are some good tools for this out there, check out bitrock, inno setup or wix.

Also Visual Studio 2010 was the last version with setup project support. It's not included in 2012.

nhahtdh

49.2k13 gold badges101 silver badges136 bronze badges

Anders M.Anders M.

Create a .bat file
Write this code:

Put this file in installer directory.

HaibaraAiHaibaraAi

Not the answer you're looking for? Browse other questions tagged visual-studio-2010setup-project or ask your own question.

Active4 years ago

I have a Visual Studio 2010 Deployment Project with the following settings:

The project I am building has several DLLs that due to the legacy way that serialization was implemented the file versions for this project can not be incremented (which we are in the process of changing).

How can I get the setup project to remove the existing files entirely (or at least overwrite with all the new files)?

Maybe I need to script an uninstall in the installer (can someone link me to do this, I can't find)

I have looked around and for any existing questions and they all say 'increment your file versions', however for me this is not currently an option.

SephSeph

6,0718 gold badges51 silver badges82 bronze badges

3 Answers

The setup project created with Visual Studio (2008 and 2010) will only replace files if the version number has been incremented. The obvious solution would be to just increment all version numbers; but as you said this is not feasible for you.

The behavior of the .msi file is basically determined by the moment when the RemoveExistingProducts action is executed. Installers created with VS 2008 schedule this action after the new product has been installed. Modified assemblies whose version has not been incremented therefore don't get replaced. Some more details about the update behavior are described in this thread:

To change the behavior, you can patch the created .msi file so that the RemoveExistingProducts action is executed before the new product gets installed (this actually has been the behavior if you created the setup with Visual Studio 2005). Patching can e.g. be done using a small VBScript that runs as a post-built step:

Dirk Vollmar