Hi
I'm just wondering if it is (or could be) possible to downgrade from a later version to an earlier one and or prevent the automatic upgrade to a later version (but allow manual upgrade).
The reason for this is that we're interfacing to third-party software which is installed & maintained manually by the customer. Quite frequently we are unable to find out what version of the third-party software the customer is actually running, because the customer representative that we're talking to doesn't know and doesn't have a rights and or skills to find out. Consequently a suck-it-and-see approach is necessary to find out what version of our software is necessary to successfully interface with the third-party software.
It would be particularly useful if the particular version to upgrade (or downgrade) to could be specified.
Many thanksRichard
I'm just wondering if it is (or could be) possible to downgrade from a later version to an earlier one and or prevent the automatic upgrade to a later version (but allow manual upgrade).
Unfortunately this isn't yet possible but something like this is in the planning stages. That is you'll be able to keep previous versions hanging around and rollback to them when/if you need to.
It doesn't sound like it would affect your situation, Richard, but in the general case, I would expect that one of the difficulties in allowing downgrades would be that the customer would (potentially) have to provide downgrade actions to complement any upgrade actions. Registry actions wouldn't necessarily be any easier, either -- if you overwrote a value in v 2.0 and you roll back to v 1.0, do you restore the original value?
I don't envy Sam and Wyatt having to worry about all of those kinds of issues.
Those are just a few of the problems. What we recommend users to do (if they require rollbacks) is to keep the initial installer hanging around on disk. Then if you need to rollback then just uninstall the current version and re-install the initial version.
This is a crude method, but it works.
...something like this is in the planning stages. That is you'll be able to keep previous versions hanging around and rollback to them when/if you need to.
I think that would be fine for our needs. Would this be tied in with preventing automatic updates, or preventing updates beyond a particular version?
You can already prevent updates on the server side of things. See: How to prevent or limit updates.
Does this help?
