Skip to content

Releases

nUpdate 5.0.0-rc.1

nUpdate 5.0.0-rc.1 Pre-release
Pre-release

Choose a tag to compare

@begerdom begerdom released this 10 Oct 22:06

The first release candidate of nUpdate 5, a complete rewrite. It is complete and tested, but details may still change before 5.0.0, so please report anything that gets in your way.

Highlights

  • Cross-platform installer. Updates install on Windows, Linux and macOS with a self-contained installer that needs no .NET on the machine, with a small window or none at all. macOS application bundles are replaced as a whole, so their signature stays intact.
  • One package per platform. A version can ship builds for Windows, Linux and macOS side by side; each client takes the one for its platform.
  • Checked before installing. Every package is verified against its size, SHA-512 hash and RSA-PSS signature.
  • nUpdate Administration on Windows, Linux and macOS, in light or dark mode. Published packages stay editable, projects are portable folders, and a migration assistant moves projects of nUpdate 3 and 4 over while both versions keep running.
  • Update dialogs for Windows Forms, WPF and Avalonia, or your own user interface on the same update flow.
  • Publishing over SFTP, FTPS and FTP or a transfer plugin, pre-release channels, rollout conditions and download statistics.

Packages

dotnet add package nUpdate --version 5.0.0-rc.1
dotnet add package nUpdate.UpdateInstaller.UI.Avalonia --version 5.0.0-rc.1

plus one of nUpdate.UI.WindowsForms, nUpdate.UI.WPF or nUpdate.UI.Avalonia for the update dialogs. nUpdate.UpdateInstaller is the base for an installer of your own, and nUpdate.Administration.TransferInterface for transfer plugins.

nUpdate Administration

File Platform Notes
nUpdate-Administration-win-x64.zip Windows x64 Needs the .NET 10 Runtime. Start nUpdate.Administration.exe.
nUpdate-Administration-osx-arm64.zip macOS, Apple silicon Self-contained. Signed ad hoc, not notarized: allow it under System Settings › Privacy & Security after the first start.
nUpdate-Administration-osx-x64.zip macOS, Intel As above.
nUpdate-Administration-linux-x64.tar.gz Linux x64 Self-contained. tar -xzf and start nUpdate-Administration/nUpdate.Administration.
nUpdate-Administration-linux-arm64.tar.gz Linux arm64 As above.

SHA256SUMS.txt lists the checksums of the files.

Moving from nUpdate 3 or 4

nUpdate 5 has new file formats and a new API. Open your project in nUpdate Administration 5: it converts the project, and the migration assistant publishes the packages for nUpdate 5 next to the old ones, so installations of both versions keep finding their updates. The README's Migrating to 5.0 explains the bridge release that moves installed copies over.

Known limitations

  • The built-in installer for Windows is not code-signed yet, so the administrator prompt shows "Unknown publisher".
  • Create packages of macOS application bundles in nUpdate Administration on a Mac: the signatures of files in Contents/MacOS that are not executables live in extended attributes, which only a Mac can read.

nUpdate v4.0

Choose a tag to compare

@dbforge dbforge released this 03 Jan 00:05
  • Removed nUpdate.ProvideTAP and nUpdate.WithoutTAP packages and replaced them with one nUpdate package
  • Upgraded nUpdate package to .NET standard 2.0
  • Upgraded all other packages and applications to .NET Framework 4.6.1 and applied the SDK project styles
  • Fixed problems with TLS 1.2 and FTPS certificates in the administration
  • Simplified the project structures
  • Removed redundant dependencies to System.Windows.Forms and others

nUpdate v3.5.0

Choose a tag to compare

@dbforge dbforge released this 27 Jul 11:56
  • Fixed possible security issue in the update installer
  • Added property to choose, if the installer should be run as admin or not
  • Wait for host process to safely exit in the update installer
  • Fixed possible NullReferenceException in the update installer

nUpdate v3.4.1

Choose a tag to compare

@dbforge dbforge released this 18 Jun 23:20

NOTICE: It is highly recommended to use the newest version of the library together with the newest one of nUpdate.Administration to ensure the mechanisms for closing a possible vulnerability are working.
You may use the newest version with an elder one for compatiblity reasons, but it is NOT recommended to do so. ARP-spoofing or a server compromising could lead to a remote code execution which is a major security flaw.
Although the package content itself is verified through a signature, the scripts of the update operations were not to this point which makes this vulnerable.
nUpdate v3.4.1 fixes this problem to make the operations part of the package content and ensure no problems can occur.

  • Fixed heavy security issue allowing a possible remote code execution
  • Fixed a vulnerability due to an older version of DotNetZip
  • Added windows event log usage to update installer for service applications
  • Fixed a bug that would recognize the app running as service although it is not when installing an update
  • Added the possibility to run operations before replacing files or folders
  • Added the "Replace files/folders" operation to the dialog for package editing
  • Added rollout conditions
  • Added WPF update installer
  • Fixed problems with unhandled exceptions in the update installer
  • Updated all dependencies to the newest version
  • Added Italian as language
  • Improved the code to prevent further bugs
  • Fixed many smaller bugs

nUpdate v3.3.1

Choose a tag to compare

@dbforge dbforge released this 30 May 19:20
  • Fixed a bug that caused that nUpdate UpdateInstaller did not install any updates

nUpdate v3.3

Choose a tag to compare

@dbforge dbforge released this 23 May 18:41
  • Fixed a possible IOException in the update installer
  • Fixed a bug where package architectures were not filtered correctly
  • Added a search timeout
  • Added the possibility to use a dynamic URI for the update packages
  • Fixed a possible InvalidOperationException in the ProjectEditDialog

nUpdate v3.2.1

Choose a tag to compare

@dbforge dbforge released this 01 Oct 20:06
  • Fixed an ArgumentNullException when no updates were found and the corresponding dialog was closed (nUpdate.WithoutTAP only)

nUpdate v3.2

Choose a tag to compare

@dbforge dbforge released this 12 Sep 22:25
  • Splitted the two build configurations for TAP and EAP into separate projects to fix dependency errors
  • Changed and improved the internal architecture of nUpdate
  • Made the Exception property in FailedEventArgs readonly
  • Fixed and improved the implementation of the async patterns
  • Fixed that a package could not be deleted when its signature was invalid
  • Improved the message informing the user about an invalid signature
  • Added renamed methods for task cancellation
  • Renamed nUpdate to nUpdate.Internal
  • Removed resource redundancies
  • Fixed a bug causing an unhandled exception when adding a file without an extension to an update package
  • Improved the ProjectEditDialog with more user interaction

nUpdate v3.1.8

Choose a tag to compare

@dbforge dbforge released this 02 Sep 22:45
  • Fixed possible unhandled errors due to problems with SQL connections in nUpdate.Administration
  • Fixed that specific events in the UpdateManager were not fired correctly
  • Fixed that nUpdate stopped updating when adding an entry to the statistics failed instead of just showing a warning
  • Fixed a bug that the application terminated when clicking "No" in the upcoming UAC prompt for starting nUpdate UpdateInstaller - now it simply continues running
  • Fixed possible uncaught exceptions when using the Taskbased asynchronous pattern and starting nUpdate UpdateInstaller fails
  • Internal improvements of some classes and implementations

nUpdate v3.1.2

Choose a tag to compare

@dbforge dbforge released this 30 Aug 19:28
  • Fixed possible issues when referencing nUpdate due to version specifications of Microsoft.Bcl.Async and System.Runtime that conflict with .NET 4 (removed now)
  • Fixed possible exception in nUpdate.Administration due to Invoke being used, even if the window had already been closed (missing window handle)
  • Small code improvements