自动更新与.NET / C＃应用程序免费的解决方案？ [英] Free solution for automatic updates with a .NET/C# app?

问题描述

从搜索我可以看到这个已经被问了一次又一次，但不是充分足够的，所以这里去。我是一个业余爱好者开发人员没有预算。一个程序我一直在开发一直需要定期错误修正，我和用户越来越厌倦了手动更新的。

From searching I can see this has been asked time and time again, but not adequately enough, so here goes. I'm a hobbyist developer with no budget. A program I've been developing has been in need of regular bugfixes, and me and users are getting tired of having to manually update.

我，因为我目前的更新在网站上通过FTP和我的下载链接的文本文件，然后希望用户将看到的解决方案有一个更新消息，终于让他们再被人打扰手动下载更新，以及坦率地说，是糟糕透顶。

Me, because my current solution of updating a text file through FTP and my download links on the website, and then hoping users will see the "there's an update message", and finally getting them to then be bothered to manually download the update, well quite frankly, is abysmal.

用户，因为，你永远要实现自动更新？ 会不会有永远的自动更新功能？如果我碰巧搞砸了更新过程中，叉子开始到达。

Users, because, well, "Are you ever going to implement auto-update?" "Will there ever be an auto-update feature?" And if I happen to screw up the update process, pitchforks start arriving.

在过去的我已经调查：

• WinSparkle - 没有在应用程序的更新，并且该DLL是500 KB。我现在的解决方案是一个少量KB的可执行文件并没有在应用程序的更新。
• .NET应用程序更新组件 - 不幸的是，我不能COM prehend文档
• 爱德华多·奥利维拉的自动更新 - 这似乎并不支持以外的任何与工作不在使用的文件。
• wyUpdate - wyBuild是不是免费的，而wyUpdate规范是可用的，它只是太复杂和费时要经过
• AppLife更新 - 同上最后一句
• 的ClickOnce - 解决方法执行发射的启动是巨大的，可怕的，不值得为这样一个简单的功能。出版是一种痛苦;手动FTP和替换的所有文件的需要服务器，而FrontPage扩展。

• WinSparkle - No in-app updates, and the DLL is 500 KB. My current solution is a few KBs in the executable and has no in-app updates.
• .NET Application Update Component - Unfortunately I can't comprehend the documentation.
• Eduardo Olivera's AutoUpdate - This doesn't appear to support anything other than working with files that aren't in use.
• wyUpdate - wyBuild isn't free, and while the wyUpdate specification is available, it's simply too complex and time-consuming to go through.
• AppLife Update - Ditto the last sentence.
• ClickOnce - Workarounds for implementing launching on startup are massive, horrendous and not worth it for such a simple feature. Publishing is a pain; manual FTP and replace of all files is required for servers without FrontPage Extensions.

这是相当令人失望的是在Windows上的情况是这样的，当你有非常好的和简单的实现用于Mac OS X如耀。

It's quite disappointing that the situation on Windows is like this when you've got really nice and simple implementations for Mac OS X like Sparkle.

推荐答案

早该此年龄前更新，哎呀！

Should've updated this ages ago, oops!

但无论如何，我一直在使用 SparkleDotNET 有一段时间了，它一直工作绝对精彩。有一些小虫子在这里和那里，但我已经帮得到他们中的一些压扁，并希望我能摆脱别人太：）

But anyway, I've been using SparkleDotNET for a while now and it's been working absolutely wonderfully. There's a few little bugs here and there but I've already helped get some of them squashed, and hopefully I'll be able to get rid of the others too :)

对于那些谁需要运行Visual Studio的发布功能的时间，并且其应用程序是相对独立的，并且不需要像启动在启动任何东西，我建议你的ClickOnce是肯定的。 MetroTwit 使用它，它有一个很好的在应用程序更新的界面，这样看来灵活的（至少在一定程度上）。对于启动在启动时，它的可能的这样做，但方法这样做是相当哈克和不工作的很好。

For those who have the time to run the publish functionality of Visual Studio, and whose app is relatively self-contained, and doesn't require anything like launching on startup, I'd recommend ClickOnce for sure. MetroTwit uses it and it's got a nice in-app updater interface, so it seems flexible (at least to a certain degree). For launching on startup, it's possible to do so, but methods to do so are quite hacky and don't work that well.

这篇关于自动更新与.NET / C＃应用程序免费的解决方案？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！