Overview
To integrate Velopack into your application, you must initialise the Velopack as early as possible in app startup, and you should add update checking code somewhere.
Update Sources
An update source tells UpdateManager where to look for your releases..json feed and the packages it references. When you pass a plain URL or file path to the UpdateManager constructor, Velopack picks a simple source for you, but you can also construct a source explicitly to get authentication, prereleases, and provider-specific behaviour.
Targeting a Specific Version
By default, UpdateManager only ever moves forward
Testing Updates
When developing applications with Velopack, you'll want to test your update logic without requiring a full installation. This guide shows you how to test updates, hooks, and other Velopack features in development and CI/CD environments.
Uninstalling
This page describes what happens when your application is uninstalled, what gets removed, and what survives.
App Hooks
Hooks allow your application to run logic at various stages of the install/update/uninstall process.
Preserving Files & Settings
Your application binary files get completely replaced during updates, so you should not store important files in the same directory as your application binary files.
Release Notes
It is possible to store release notes (Markdown) in update packages and access it while Updating. This could be useful, for example, to show a user a list of changes before downloading a update.
Windows Shortcuts
By default, during installation Velopack will create a shortcut on the Desktop and in the StartMenuRoot. It will automatically delete any shortcuts it finds when uninstalling the application.
Switching Channels
By default, UpdateManager will try and search for releases in the same channel that it was built for. You can read more about packaging channels here. So normally, you should not provide a channel at all to the UpdateManager constructor.