限制 ClickOnce 部署服务器上的版本
从这个 StackOverflow 答案的声音来看，当我发布我的应用程序供我们公司内部使用时，我必须手动从 [Publish Directory]\Application Files 中删除旧的“版本”。
我假设这是正确的，但是这样做有什么后果吗？我读过 ClickOnce 确实合并了对应用程序设置的更改，但它是否需要其他版本来修补升级应用程序？
我担心这样的情况：我有一个用户跳过了一个或两个版本的升级，当他们决定升级 ClickOnce 架构时，要求部署文件夹包含所有版本和当前部署最多的版本才能升级。
这对我来说似乎不太合理，但有人可以确认我在文件夹中需要的只是最新版本吗？此外，任何编写 Windows 任务来清理除最新版本之外的所有旧版本的帮助都会非常有帮助！
From the sounds of this StackOverflow answer it seems that when I publish my app for our company to use internally I have to manually remove the older "versions" from [Publish Directory]\Application Files.
I'm assuming this is correct, but is there any consequence to doing this? I've read that ClickOnce does merging changes to application settings, but does it need the other versions for patching an upgrading app?
I'm concerned about the scenario where I have a user that has skipped upgrading for a version or two and when they do decide to upgrade the ClickOnce architecture requires that the deployment folder contain all the versions and the current most deployed version in order to upgrade.
This doesn't seem plausable to me, but can someone confirm that all I need in the folder is the latest version? Also, any help in writing a Windows task to clean out all the older versions except the most recent would be very helpful!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我假设您正在使用 Visual Studio 进行发布。如果是这样，每次发布时都会发布整个应用程序。每个发布的版本都是相互独立的。除了备份之外，无需保留以前的版本。
I assume you are using Visual Studio to publish. If so, every time you publish it publishes the entire application. Each published version is independent of one another. No need to keep previous versions other than having a backup around.