PDA

View Full Version : Full History Patch


greenace
02-03-2004, 12:03 PM
I have an application that is updated almost monthly - and there are currently many versions in the field. I want to set-up a Full-History Patch, but I don't have the file information for every single release.

Is there a way to update all version to the current version if I do not have the files/version history for each version?

Also, what is a good technique used to maintain a record of all versions and their files. I use Setup Factory to build my installations - and any time there has been a change, I just recompiled a new setup file. My application also used True Update to download any updates - and install them.

Perhaps there is a document that shows the general workflow - and interaction between IndigoRose Applications.

Adam
02-13-2004, 03:35 PM
greenace,

If you do not know any information about past files then a patch turns into a setup. I would use Setup Factory (like you are) and keep track of the files. The best way to keep track of files is to archive them in folders that are name 1.0.0.0 and 1.0.0.1 ie their version number or some other descriptive word.

As far as general workflow between IndigoRose products the possibilities are almost endless. I will explain the classic software approach workflow.

- Use Setup Factory to create your initial installs. We create a new setup for every version to avoid having new customers go through the update process. You can just create the initial one and let you system take it from there.

- Use Visual Patch to create your patches every time a new version is released. This process speaks for itself but you must have a log of the files that were included in every previous version.

- Use True Update to check for new versions on the net. When a new version is needed download and run the patch that was created with Visual Patch. True Update has the download actions that will take care of this process.

These are not set rules of use, rather this is just one way to use our products together to distribute, and update your software with very little user knowledge of what is going on behind the scenes.

I hope that this helps.

Adam Kapilik