寻找在 ClickOnce 应用程序中显示发行说明的建议
我有一些策略，我将在一些场景中进行尝试，并正在寻找其他人已经有过的经验并证明是成功的指导。
我当前想到的策略是：
- 将release-notes.xml 文件放在发布位置的根目录中，其中包含格式化注释，应用程序在检测到可用的新版本时可以手动下载这些注释。
- 使用
FileGroup并使用ApplicationDeployment.DownloadFileGroup(String)下载该组，其中包含上述发行说明。
我只想要更新之前的发行说明。我自己通过 ApplicationDeployment.CheckForUpdateAsync 处理应用程序更新，并通过应用程序状态栏通知用户，并考虑允许他们在启动应用程序更新之前查看已更改的内容。
非常欢迎任何其他建议。
我应该明确指出，发行说明的用例是在更新之前，以便用户确定当时是否应该选择更新。
I have a few strategies which I'm about to trial in a few scenarios and am looking for guidance on what others have had experience with and proven successful.
The current strategies I have in mind are:
- Place a release-notes.xml file in the root of the publish location which contains formatted notes that the application can manually download when it detects a new version available.
- Use a
FileGroupand download that group usingApplicationDeployment.DownloadFileGroup(String)which would contain the said release notes.
I only want the release notes prior an update. I'm handling application updates myself through ApplicationDeployment.CheckForUpdateAsync and notifying the user through the application status bar and was thinking of allowing them to view what has changed prior to initiating the application update.
Any other suggestions are very much welcome.
I should make it clear that the use case for the release notes are prior to an update to allow the user to determine if they should choose to update at that time or not.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
你的建议听起来很有道理。但是，我会尝试使其尽可能简单...
System.Diagnostics.Process.Start(relaseNotesUrl);What you are suggesting sounds plausible. However, I would try keep it as simple as possible...
System.Diagnostics.Process.Start(relaseNotesUrl);我同意代码震荡。您还可以使用 ApplicationDeployment.IsFirstRun 来判断用户是否安装了新版本。更新后或第一次安装后确实如此。但由于您是以编程方式进行更新，因此您可能只需弹出 Web 浏览器即可。
I agree with codeConcussion. You can also use ApplicationDeployment.IsFirstRun to tell if the user has installed a new version. It's true after an update or after the 1st installation. But since you're doing the updates programmatically, you can probably just pop up the web browser at that point.