I have a program that has several pieces to it that may have an update available. For example, I have a price file that is periodically updated, even though the program has not changed. Can I handle this in a single True Update client application?
I was thinking I could set up a version for each case. So there would be a Version for people with the current price file, and a version for people without the current price file.
Then it hit me, does TU only process the first version that matches the version identifiers, or can it continue and process additional versions that also match version identifiers.
As an alternative, it looks like I must distribute 2 separate True Update executables - and this gets to be a size concern.
Any thoughts?
I was thinking I could set up a version for each case. So there would be a Version for people with the current price file, and a version for people without the current price file.
Then it hit me, does TU only process the first version that matches the version identifiers, or can it continue and process additional versions that also match version identifiers.
As an alternative, it looks like I must distribute 2 separate True Update executables - and this gets to be a size concern.
Any thoughts?
Comment