Creating an update patch 1

[steve1rm]

Hello,

Does anyone know how to make an update patch for a VS 2005 window project.

I have developed a CRM for some customers. However, the customers want some more development to it.

I am wondering is there any way you can create an update patch that will only install the changes or add-ons that you have made. Currently the users have to uninstall and then install the new setup.

I have used MSI to create the setup.

Many thanks for any suggestions,

Steve

 

[cjelec]

This is always an interesting subject.

You wouldn't be able to update a single exe application, instead you can split your application into separate dll's and/or code files (good for add-ons), then copy new files over them.

You can then have another application to perform the update:
1) Checks the server for updates
2) Downloads the latest update (simple If NewUp > OldUp ... code)
3) Checks to see if the app is currently running, if so shuts it down (you could do this with a change to the registry and the main app looks for the change, a Timer...)
4) A little script based copying of files from the download to the apps folder (this could be in lines: "MyFile.dll > %appfolder%\MyFile.dll")
5) Restart the app?

Backing up the old files could be a good option to give the customer, the user can then just revert back to the last working version if the new one goes funny...

You could use cab or zip files to contain the updated files, or you could create your own file format that contains everything (script & files)...

If you need any more help on this, then please ask

 

[Aptitude]

When you create a setup project you can set the RemovePreviousVersions property to true. This will stop your users having to uninstall before installing the new version as the installer does this step automatically.

Just ensure that you never change the ProductCode property between versions otherwise the installer will never find the previous version's uninstaller.