AutoUpdater.NET VS Squirrel

It's not a website, it's a project.

You could also maybe check out AutoUpdater.NET as another possibility.

Aa others mentioned, it just more common to have an auto-updater mechanism built-in in your app. Check out AutoUpdater.NET which periodically check the server for new versions, download it in background and allow you to present a "update ready" button to the user that quickly restart the app to the new version when they are ready to apply it. A bit like the Chrome or Discord update ready buttons.

Good catch. Hmm, looks like Squirrel might be a no go. Oh well. My examples were not heavily researched. Just something to point in a starter direction. At a glance this looks promising too: https://github.com/ravibpatel/AutoUpdater.NET

Libraries like https://github.com/ravibpatel/AutoUpdater.NET, and plenty of others. This may not fit your needs, but maybe it does.

But it AutoUpdater.NET(https://github.com/ravibpatel/AutoUpdater.NET) does quite the same. It only looks at your own server instead of github. You should be able to get an idea of how it works and how to implement it using github instead.

I have a few desktop apps that uses AutoUpdater.NET to update the app on startup, as well as one app that's linked to a mapped drive. Since both apps are self-contained, it's always been a pain to update them - you either have to copy the entire 150 MB publish directory to your update location, or you have to pick and choose which binaries were updated, which you'd then push into a ZIP folder.

I never had much luck with ClickOnce, so I was using Squirrel.Windows. I've recently switched to the Clowd.Squirrel fork, since I needed support for AzureSignTool in the build process.

As soon as Office 2007 didn't use MSI the format was doomed.

I assume the Here in NIH refers to an individual team, not MS as a whole.

Teams is entirely NIH https://github.com/Squirrel/Squirrel.Windows for updates to the Electron app.

I would use winget, but MS made it weirdly hard to run as a script on multiple computers, it installs per user, because... who knows.

So still using chocolatey

Back in the day, wasn't Discord installed using Squirrel?

Originally, we used to use Squirrel.Windows for our internal applications but we had a few issues with it before we finally dropped it.

The most viable option with the path of least resistance would be Squirrel.Windows as it is both and installer and updater but has some caveats (SemVer pattern must be followed).

Maybe someone has a better ide, but this is one of many reasons why I'm trying to get all our old ClickOnce installers migrated to something else (I've heard good things about Squirrel.

Electron does have auto-update built in (Squirrel), but it comes with severe non-price related caveats. Squirrel is only intermittently maintained and goes through long periods in which the different versions are abandoned (see for Windows, macOS). People have requested a switch to Sparkle on macOS, which is what Conveyor uses, but with no response. There's also the issue that their update solutions require interactive servers but the only free one is restricted to open source projects, and isn't itself open source. The Electron website points you towards a variety of projects if you want to run your own server but all of them are (again) abandoned for years.

We replaced clickonce with https://github.com/Squirrel/Squirrel.Windows and are generally happy with the choice

Discord in the Task Manager can sometimes show up as "Update", made by GitHub, because Discord uses a program, that GitHub / their devs were/are involved with making, to update the app, and some kind of bug happens that means it doesn't display as 'Discord'.