Hey Joerg,
You can both limit updates and do "offline updates". To limit updates, do something like this: How to prevent or limit updates.
To do offline updates use the %updatepath% variable and the -updatepath commandline switch.
Configurable updates by customer
evelixI'm looking into your product and have one use case, where I didn't find the answer to on your site.
When selling ISV software to goverment agencies or large companies, they typically restrict users from installing anything themselves. Also the IT departments usually don't like it, if the program wants to update itself. They like to be in control.
So I'd like to be able to use the auto updater system "as is" for normal customers, that have the ability (rights) to download and install newer versions of the software. For other customers I'd like to be able to configure the application to look for newer versions on a local network folder and if a newer version is found, it will be updated, using username, password credentials stored somewhere in the network folder using impersonation. Of course this network folder is under control of the local IT department and it would store the files there, that I will provide and yes username and password would need to be protected/hashed.
As this is dynamic, the users would need to be able to set this network direcotry somewher in the options of the application.
Is something like this possible? Advantage would be, that newer versions of our software would be easier to spread to our customer base, as usually this would require the local IT department to create a distribution package, which is (can be) very lengthy process with goverment or large companies.
Any thoughts about this, or am I off the wrong path, alltogether?
Joerg