Updating, Upgrading or Patching a .Net Application

Vivek

18y4.8k

We have a .Net application that sometimes has to be:

1. Patched (with very minor changes in source code)
2. Updated (with small, but notifyable changes in the modules)
3. Upgraded (major changes to the application)

At the end, the updated assemblies are to be replaced on the target machine. For this, currently we uninstall the existing version of application on the machine and then run the newly created installer. This process is very tedious and time consuming.

Also, being change of just fistful assemblies, its not worthwhile to waste time in uninstall and reinstall the entire application.

Does anyone have a smart way to simply REPLACE the existing the older assemblies with the newer one USING Visual Studio INSTALLER?

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Travis18y ago
His answer is the easiest thing I can think of, however; I would love to hear other input as I am soon going to be in the same boat with an application that I just rolled out.
Ryan Alford18y ago
you can make the installer uninstall the previous version during it's installation. You can do this by setting the "RemovePreviousVersions" to "True". Also, if you do this, you will always need to change the "Version" property of the installer. This is what the installer uses to tell another version is installed. When you change the "Version", you will be prompted to change the Product Code also. Just click "YES", and Visual Studio will change the Product Code for you. This is how I deploy changes.