单击一次重定向
是否可以部署一个应用程序（使用现有的 clickonce 部署 URL，以便用户更新到该版本），从而更改已部署应用程序的部署 URL？
场景是，我有一个已部署的客户端（A），它很稳定并且已经使用了一年多，还有一个新的客户端（B），它正在开发中并将使用。但是，B 和 A 具有不同的 UID，因此它们可以一起部署在同一系统上。在将来的某个时候，我希望自动将一直使用 A 的用户迁移到 B，但我希望 Clickonce 设计得足够好，如果我将 B 的安装文件放在 A 的安装中，就不会将 A 升级到 B目录（因为它应该检查这些 UID）。
我知道通过 clickonce 部署的 C# 应用程序可以访问其自己的部署方法，并且我想知道是否能够更改升级位置。
我希望在没有用户太多参与的情况下安静地完成此操作（并且我知道安静的重定向是非常不受欢迎的，有充分的理由）并且想知道是否有人有尝试修改已安装的 clickonce 的部署/升级信息的经验更新。
Is it possible to deploy an application (using an existing clickonce deployment URL, such that users update to that version) which changes the deployment URL of the deployed application?
The scenario is that I have a deployed client (A), which is stable and has been in use for over a year, and a new client (B), which is in development and will be used. However, B and A have different UIDs so that they can both be deployed on the same system together. At some point in the future, I'd like to automatically migrate users who have been using A to B, but I'd hope that Clickonce is well-designed enough to not upgrade A to B if I place B's install files in A's install directory (because it should be checking those UIDs).
I know that a C# application that's been deployed through clickonce has some access to its own deployment method, and I'm wondering whether I'm able to change the upgrade-location.
I'm hoping to do this quietly without much involvement of the user (and I understand that quiet redirects are heavily frowned upon, for good reasons) and am wondering whether anyone has any experience of trying to modify an installed clickonce's deployment/upgrade information with an update.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
出于显而易见的原因，我不知道您是否能够安静地完成此操作，但您也许可以通过协助卸载并提供新部署 URL 的指示来帮助用户。您可以连接到 ApplicationDeployment 并在 clickonce 升级期间运行您自己的自定义安装代码，因此，在用户许可的情况下，您可以自动化整个过程。
至于简单地重定向到单独的部署 URL，我想说我从未尝试过，但我认为它不会起作用。
I don't know that you would be able to do it quietly, for obvious reasons, but you might be able to help a user along by assisting with an uninstall and providing directions to a new deployment URL. You can hook into the ApplicationDeployment and run your own custom installation code during a clickonce upgrade, so you may, with user permission, be able to automate the whole thing.
As far as simply redirecting to a separate deployment URL, I'm going to say that I've never tried, but I don't think it will work.