Where you say:
My apps should all still use it if it's installed, but I have definitely stopped "promoting" it, as I essentially gave all my apps the ability to CHECK for updates using code built into them (DcUpdater will download and run the installler).
So anyway, DcUpdater is not really needed anymore, and it does seem a bit overkill.
I appreciate what you say there, but I'm a fan of DCUpdater's, because it saves me some time/trouble.
I have long preferred to use DCUpdater
to auto-manage updates (i.e., check for new version, download, install) for all DC apps.
, all in a single
operation, rather than get each app to update itself on an ad hoc
basis using DCUpdater. I regularly launch DCUpdater from a FARR button, and it does any update checks/installs in one fell swoop.
This necessitated a bit of careful organisation, initially, of the two files:
- [Name of app].dcupdate
- [Name of app].dcupdateredirect (contains the explicit path to the app. folder)
- but, once done, it's a breeze.
By organisation, I mean there is a copy of both of the above files in each
DC app. folder, and a copy of every [Name of app].dcupdateredirect
I keep all the apps. (including DCUpdater) in folders within a Plugins subfolder to FARR: C:\UTIL\Windows utilities\FindAndRunRobot\Plugins\
All the apps. have ConfigDir.ini
files set with:
- CONFIGDIR = .
- which all seems to work OK (most of the time).
DCUpdater thus outputs useful/helpful/informative reports like this, when it runs, and it's very fast: