nUpdate 5 release candidate · MIT licensed · .NET Standard 2.0
Publish packages from nUpdate Administration to your own server. A few lines of C# find, verify and install them, and the installer needs no .NET on the machine.
Updating Aurora
Installer from nUpdate.Installer/win-x64/, self-contained, with your app's icon, or no window at all.
How it works
nUpdate Administration builds one zip per platform, signs it with your project's key and uploads it with nupdate.json over SFTP, FTPS or FTP.
UpdateManager reads the feed, picks the zip for its runtime identifier and checks size, SHA-512, the RSA-PSS signature and the manifest before anything runs.
The installer waits for your app to close, runs your operations, replaces the files and restarts it, with a small window or, on a server, without one.
One version, a build per platform
A client looks for its runtime identifier, then its operating system, then any. A version without a fitting file is simply not offered. Pick a client to see which file of version 2.2.0 it installs.
win-x64 takes win-x64.zip: the exact runtime identifier.
What you get
Every package is checked against the feed and your key before the installer starts. The signed manifest must also name your project, the version and the platform, so a feed cannot hand out a relabelled package.
Self-contained single files for win, linux and osx on x64 and arm64. A small window that follows light and dark mode, or none at all for services and servers. Every run writes install.log.
The installer builds MyApp.app.new next to your app and swaps the two atomically, so the bundle is never half there and its signature stays intact.
Offer betas to the users who want them, ship to one ring or region first and mark updates that must not be skipped. A beta channel also receives release candidates and releases.
manager.MinimumStability = Stability.Beta;
manager.RolloutConditions["Ring"] = "early";Update dialogs for Windows Forms, WPF and Avalonia, or your own on the same update flow. Even the installer window can be your own executable.
Delete and rename files, start and stop processes everywhere. Registry keys and services on Windows. Wait for a migration tool and fail the update if it fails.
Packages and the feed are plain files on any web server. Download statistics are optional, through a small PHP and MySQL endpoint you host yourself.
Get started
The library targets .NET Standard 2.0, so it runs in .NET Framework 4.6.2 apps as well as on .NET 10. The installer package copies the right installer next to your app on build.
dotnet add package nUpdate --version 5.0.0-rc.1
dotnet add package nUpdate.UpdateInstaller.UI.Avalonia --version 5.0.0-rc.1
[assembly: ApplicationVersion("1.0.0")]
var manager = new UpdateManager(
new Uri("https://example.com/updates/nupdate.json"),
publicKey);
if (await manager.CheckForUpdatesAsync())
{
await manager.DownloadAsync(progress);
if (await manager.VerifyAsync())
manager.StartInstaller(); // installs and restarts the app
}// nUpdate.UI.WindowsForms, nUpdate.UI.WPF or nUpdate.UI.Avalonia
var updaterUI = new UpdaterUI(manager, this)
{
UseHiddenSearch = true // stay quiet when there is nothing new
};
var result = await updaterUI.RunAsync();
// Brand the installer window too
manager.InstallerIcon = Path.Combine(
AppContext.BaseDirectory, "app-256.png");
manager.InstallerAccentColor = "#2E7D32";<ItemGroup>
<PackageReference Include="nUpdate" Version="5.0.0-rc.1" />
<PackageReference Include="nUpdate.UpdateInstaller.UI.Avalonia"
Version="5.0.0-rc.1" />
</ItemGroup>
<!-- The installers you ship, copied to nUpdate.Installer/<rid>/ -->
<PropertyGroup>
<nUpdateInstallerRuntimes>win-x64;osx-arm64</nUpdateInstallerRuntimes>
</PropertyGroup>// A whole installer on nUpdate.UpdateInstaller
[STAThread]
static int Main(string[] args) =>
InstallerHost.Run(args, session => new MyWindow(session));
sealed class MyWindow(InstallerSession session)
: WindowProgressReporter(session)
{
protected override void ShowProgress(float progress, string text)
{
/* your progress bar */
}
// RunWindow, Post, AskAboutLockedFile, ShowError, Finish
}nUpdate Administration
A project is a folder you can copy to any machine. Secrets are encrypted with a project password, servers are trusted by fingerprint, and download statistics come from a small PHP and MySQL endpoint. Published packages stay editable: change their files or operations, and nUpdate Administration builds the changed platforms again and replaces them on the server. It follows the light or dark mode of your system.
Aurora - nUpdate AdministrationEdit package 2.1.0 of AuroraAurora - nUpdate AdministrationMove Aurora to nUpdate 5Every package of updates.json with the version it gets in nUpdate 5. Applications built with nUpdate 5 only install versions newer than their own, so packages older than your first nUpdate 5 release only complete the history; you can leave them out.
3 of 3 packages to migrate selected.Coming from nUpdate 4?
1.2.0.0b1 becomes 1.2.0-beta.1.win-x86 and win-x64; ready for Linux and macOS builds next to them.nUpdate is free and MIT licensed, built and maintained in spare time. If it keeps your users up to date, a donation helps it keep going.