mirror of
https://github.com/velopack/velopack.git
synced 2025-10-25 15:19:22 +00:00
9ccb224815
Removed numbering on file naming and separated into separate sub-directories for getting-started, using, and contributing.
26 lines
1.5 KiB
Markdown
26 lines
1.5 KiB
Markdown
| [docs](..) / [using](.) / update-process.md
|
||
|:---|
|
||
|
||
|
||
# Update Process
|
||
|
||
The following steps are performed by the `UpdateManager` each time your app is executed:
|
||
|
||
1. **Check for Updates** - the `RELEASES` file at the distribution location is downloaded and compared to local `RELEASES` file to check for any updates.
|
||
2. **Download & Verify Update Packages** - if there is a new release, the `UpdateManager` determines whether to download the deltas or the latest full package to update to the current version. The packages are compared against their SHA1 in the `RELEASES` file for verification.
|
||
3. **Build Full Package from Deltas** - if delta packages were downloaded, a new full package is created from the previous full package and the downloaded delta file.
|
||
3. **Install New Version** - the current version of MyApp is extracted from the full package and placed in a new `%LocalAppData%\MyApp` install directory based on the version number (e.g., `app-1.0.1`).
|
||
4. **Update Shortcuts** - desktop and Windows Start Menu shortcuts are updated to point to the new MyApp version (via the `--processStart` command line parameter passed to `Update.exe`).
|
||
5. **Previous Version Clean-up** - on the next startup of MyApp, the previous packages and installed app directory of all but the previous install are also deleted.
|
||
|
||
## See Also
|
||
|
||
* [Update Manager](update-manager.md) - reference guide for the `UpdateManager`.
|
||
* [Debugging Updates](debugging-updates.md) - tips on debugging your Squirrel application.
|
||
|
||
|
||
---
|
||
| Return: [Table of Contents](../readme.md) |
|
||
|----|
|
||
|