问题
On the Mac there's a really nice library called Sparkle that programs can use to implement the checking/install functionality for auto-updates.
Is there anything similar out there for .NET? Or just regular Win32?
回答1:
ClickOnce has its own security limitations (understandbly so). If you want the full power and control of a Windows application then go with the .NET application updater component. It works like a charm and has even been used by Microsoft internally for their .NET based game (I don't remember the game name though).
回答2:
Let me start by saying we offer a complete updating solution which includes:
- An open source updater, wyUpdate, written in C#
- The free AutomaticUpdater control that you can just add to your .NET app's form
- wyBuild is used to build patches and manage your versions
wyUpdate handles all of the Vista/Windows 7 UAC problems and all the file permission problems that inevitably pop up when you're trying to update complex software.
That being said, if you want to build your own updater here are some tips:
Building your own updater
A good place to start is the wyUpdate C# source code I mentioned above. You can cannibalize it and use it for your own purposes. Some of the algorithms it contains:
- Full Windows Vista / Windows 7 UAC support
- Ability for limited users to check and then update if they have credentials
- Support for wonky corporate inernet. (If you've ever worked with a corporation this is a real problem).
- Quick extracting, patching, and installing of files.
- Registry support.
- Roll back files & registry on error or cancellation by the user
- Self-update (no files left behind)
We also have the file specifications here.
Automatic updating
Since being automatic is a requirement let me tell you how we do it with our AutomaticUpdater control.
We use named pipes to communicate between the standalone updater (wyUpdate) and the Automatic Updater control sitting on your program's form. wyUpdate reports progress to the Automatic Updater, and the Automatic Updater can tell wyUpdate to cancel progress, to start downloading, start extracting, etc.
This keeps the updater separate from your application.
In fact, the exact named pipes C# code we use is included in an article I wrote a little while back: Multi-process C# app like Google Chrome.
回答3:
ClickOnce is my preferred method. It has some warts, but it comes with Visual Studio and works reasonably well.
回答4:
ClickOnce is heavily used, but you can do what I did for a large application and try these:
Application Auto Update in VB.NET
Application Auto Update Revisited
I tinkered with the logic a bit and built what I thought was a better XML update file. Now, when I need to update the clients, I just post the new EXE files or DLL files and set the correct versions in the public XML file. My application detects the newer versions if it is older and updates itself. If you are doing this on Windows Vista, you need to prompt for administrator permissions so that Program Files can be written to (if you install there).
You can also easily convert this to C# using C#/VB.NET Converter.
回答5:
I just went through the process of doing this and used NetSparkle.
It worked as advertised for a Windows Forms application with an MSI installer that overwrites the previous version. I'm very glad I found it too -- I was about to roll my own. Am I the only one making really simple .NET applications? Mostly everything I looked at seemed like a complete overkill.
回答6:
I didn't try NetSparkle yet (I will later), but it seems it's what you're looking for.
NetSparkle is an easy-to-use software update framework for .NET developers on Windows, Mac or Linux. It was inspired by the Sparkle project for Cocoa developers and the WinSparkle project (a Win32 port).
回答7:
I think WyBuild is good Sparkle alternative )
回答8:
Here's an open-source solution I wrote to address specific needs we had for WinForms and WPF apps. The general idea is to have the greatest flexibility, at the lowest overhead possible.
So, integration is super-easy, and the library does pretty much everything for you, including synchronizing operations. It is also highly flexible, and lets you determine what tasks to execute and on what conditions - you make the rules (or use some that are there already). Last but not least is the support for any update source (web, BitTorrent, etc) and any feed format - whatever is not implemented you can just write for yourself.
Cold updates (requiring an application restart) are also supported, and done automatically unless "hot-swap" is specified for the task.
This boils down to one DLL, less than 70kb in size.
More details at http://www.code972.com/blog/2010/08/nappupdate-application-auto-update-framework-for-dotnet/
Code is at http://github.com/synhershko/NAppUpdate (Licensed under the Apache 2.0 license)
I plan on extending it more when I get some more time, but honestly you should be able to quickly enhance it yourself for whatever it currently doesn't support.
回答9:
There is a really nice utility called Updater. It looks like it is written in C or C++. I have been able to configure the XML files and load them to the production server, and then I can have the Updater Run and check the XML file for a different version and download a new update install package that I built using the Nullsoft Scriptable Install System (NSIS).
回答10:
We investigated a handful of options and decided to use AppLife Update. AppLife Update can quickly and easily add auto update functionality for your .NET applications, but it is also flexible because of its comprehensive API.
See the full list of features and some demo videos on their website.
回答11:
DotNetAutoUpdate
I've implemented a library to do this called DotNetAutoUpdate (original name eh?). It aims to be:
- Simple to use
- Simple to setup
- Secure
回答12:
For updating .Net client applications, take a look at AppLife Update. It is very flexible, extensible and customizable.
Disclaimer - I am associated with AppLife Update.
来源：https://stackoverflow.com/questions/691663/auto-update-library-for-net