Cyberduck Mountain Duck CLI

Changes between Initial Version and Version 2 of Ticket #9782


Ignore:
Timestamp:
Dec 8, 2016 11:24:13 PM (3 years ago)
Author:
Hackintosh HD
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9782

    • Property Summary changed from Cyberduck Auto-Updater ignores custom installation locations on Windows to Cyberduck auto-updater ignores custom installation locations on Windows
  • Ticket #9782 – Description

    initial v2  
    33The Cyberduck Windows installer accepts custom installation locations: Providing an installation path like e.g. ''D:\Program Files (x86)\iterate\Cyberduck'' within the installer's GUI is definitely possible.
    44
    5 Once Cyberduck is installed, however, and a new version number gets available through the auto-updater, the '''auto-update feature ''ignores'' custom installation locations''' and updates any Cyberduck installation to %ProgramFiles(x86)%\Cyberduck, no matter which installation path was initially chosen on setup. In the end, this results in ''two'' Cyberduck instances on the very same machine:
     5Once Cyberduck is installed, however, and a new version number gets available through the auto-updater, the '''auto-update feature ''ignores'' custom installation locations''' and updates any Cyberduck installation to ''%ProgramFiles(x86)%\Cyberduck'', no matter which installation path was initially chosen on setup. In the end, this results in ''two'' Cyberduck instances on the very same machine:
    66
    77* The remaining old version in the custom installation path provided in the initial setup,
swiss made software