blocks|key|1525130|text|通常，您会将新文件下载到单独的区域。然后关机并重新启动，然后在启动时查找并使用新文件(如果找到)。总是将最新的已知工作版本放在一边，以便用户可以在下载导致问题时恢复到肯定有效的版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1525131|ClickOnce是微软的一项优秀技术，它可以为您完成此任务，您可以直接在Visual+Studio2008中使用它。|1525132|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Usually you would download the new files into a separate area. Then shutdown and restart and at startup you look for and use the new files if found. Always keeping a last known working version on the side so that the user can revert to something that definitely works if the download causes problems.

ClickOnce is a good technology from Microsoft that does this for you and you can use it directly from Visual Studio 2008.

blocks|key|1740248|text|我有一个独立的“启动器”应用程序，通过web服务检查更新。如果有更新，它会下载它们，然后执行我的应用程序，该应用程序位于一个单独的程序集中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1740249|其他的选择是使用ClickOnce之类的东西，或者像其他人提到的那样，将文件下载到单独的区域并重新启动应用程序。|1740250|不过，要注意ClickOnce+-它并不像听起来那么灵活。如果你部署到一个需要将你的程序提升到更高的安全级别才能运行的系统，如果你没有为你的应用程序安装证书，你可能会遇到问题。当涉及到ClickOnce时，我发现很难在互联网上获得证书管理等问题的直接答案。如果你有一个复杂的应用程序，你可能只想滚动你自己的更新程序，这就是我最终不得不做的。|1740251|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I have a seperate 'launcher' application that checks for updates via a web service. If there are updates, it downloads them and then executes my application, which is in a seperate assembly.

The other alternatives are using things like ClickOnce, or downloading the files to a seperate area and restarting the app, as someone else mentioned.

Be warned about ClickOnce, though - it's not as flexible as it sounds. And if you deploy to a system that requires elevating your program to a higer security level to run, you might run into problems if you don't have a certificate for your app installed. I found it very difficult to get straight answers on the Internet to things like certificate management when it comes to ClickOnce. If you have a complex app, you may want to just roll your own updater, which is what I ended up having to do.

blocks|key|1525248|text|你必须关闭你的应用程序并重新启动它，因为其他人已经评论过了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1525249|我写了一个开源代码来在透明模式下做到这一点-包括一个外部更新应用程序来执行实际的冷更新。请参阅http://www.code972.com/blog/2010/08/nappupdate-application-auto-update-framework-for-dotnet/|offset|length|1525250|代码位于http://github.com/synhershko/NAppUpdate+(在Apache2.0许可下获得许可)|1525251|entityMap|0|LINK|mutability|MUTABLE|url|http://www.code972.com/blog/2010/08/nappupdate-application-auto-update-framework-for-dotnet/|1|http://github.com/synhershko/NAppUpdate^0|0|1B|2K|0|0|4|13|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

You'll have to shutdown your application and restart it, as other people have already commented.

I wrote an open-source code to do just that in a transparent mode - including an external update application to do the actual cold update. See <a href="http://www.code972.com/blog/2010/08/nappupdate-application-auto-update-framework-for-dotnet/" rel="noreferrer">http://www.code972.com/blog/2010/08/nappupdate-application-auto-update-framework-for-dotnet/</a>

The code is at <a href="http://github.com/synhershko/NAppUpdate" rel="noreferrer">http://github.com/synhershko/NAppUpdate</a> (Licensed under the Apache 2.0 license)

blocks|key|1525307|text|如今，如果你的应用程序打包在MSIX包中，Windows就可以用AppInstaller自动为你做这样的更新。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1525308|它将应用程序的新版本下载到ProgramFiles\WindowsApps中的另一个文件夹中，然后当用户通过开始菜单运行应用程序时，系统就知道应该使用哪个文件夹。以前的版本在不使用时会被删除。|offset|length|style|CODE|1525309|如果你想知道如何以这种方式打包你的应用程序，我在this+answer上收集了我的发现。|1525310|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/67636323/3087417^0|0|D|O|0|O|B|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

These days Windows can do such updates automatically for you with AppInstaller if your app is packaged in the MSIX package.
It downloads the new version of the app in another folder inside <code>ProgramFiles\WindowsApps</code>, then when a user runs the app via the start menu, the system knows what folder it should use. The previous version gets deleted when not in use.
If you want to know how to package your app this way I collected my findings in <a href="https://stackoverflow.com/a/67636323/3087417">this answer</a>.

When creating an auto updating feature for a .NET WinForms application, how does it update the DLLs and not affect the currently running application?

Since the application is running during the update process, won't there be a lock on the DLLs (because those DLLs will have to be overwritten during the update).

Auto update for WinForms application

为.NET WinForms应用程序创建自动更新功能时，如何更新DLL而不影响当前正在运行的应用程序？由于应用程序是在更新过程中运行的，因此不会对DLL进行锁定(因为这些DLL必须在更新过程中被覆盖)。

问WinForms应用程序的自动更新
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WinForms应用程序的自动更新EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WinForms应用程序的自动更新
EN