ClickOnce 错误,无法激活早期版本的部署

发布于 2024-12-17 01:29:56 字数 1925 浏览 1 评论 0原文

我有一个单击一次应用程序,清单中没有所需的最低版本,但我收到以下错误。我该如何解决这个问题?可能是什么原因造成的?我让用户卸载该应用程序,然后通过向他们提供生产 URL 来安装它。

应用程序摘要

  • 可安装的应用程序。
  • 信任 url 参数已设置。

错误摘要

以下是错误摘要,这些错误的详细信息稍后在日志中列出。

组件存储事务失败摘要

未检测到事务错误。

警告

在此操作过程中没有出现任何警告。

操作进度状态

错误详细信息

在此操作期间检测到以下错误。 * [11/18/2011 10:22:21 AM] System.Deployment.Application.DeploymentException(订阅状态) - 无法激活版本早于应用程序当前最低所需版本的部署。 - 来源:System.Deployment - 堆栈跟踪: 在 System.Deployment.Application.SubscriptionStore.CheckMinimumRequiredVersion(SubscriptionState subState,AssemblyManifest 部署) 在 System.Deployment.Application.SubscriptionStore.CheckDeploymentSubscriptionState(SubscriptionState subState,AssemblyManifest 部署) 在 System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc) 在System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(UriactivationUri,布尔isShortcut,字符串textualSubId,字符串deploymentProviderUrlFromExtension,BrowserSettings browserSettings,字符串& errorPageUrl) 在 System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(对象状态)

I have a click once application with no minimum required version in the manifest and yet I am getting this error below. How can I resolve this issue? What could be causing this? I had the user uninstall the application and then install it by giving them the production URL.

APPLICATION SUMMARY

  • Installable application.
  • Trust url parameter is set.

ERROR SUMMARY

Below is a summary of the errors, details of these errors are listed later in the log.

COMPONENT STORE TRANSACTION FAILURE SUMMARY

No transaction error was detected.

WARNINGS

There were no warnings during this operation.

OPERATION PROGRESS STATUS

ERROR DETAILS

Following errors were detected during this operation.
* [11/18/2011 10:22:21 AM] System.Deployment.Application.DeploymentException (SubscriptionState)
- Cannot activate a deployment with earlier version than the current minimum required version of the application.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SubscriptionStore.CheckMinimumRequiredVersion(SubscriptionState subState, AssemblyManifest deployment)
at System.Deployment.Application.SubscriptionStore.CheckDeploymentSubscriptionState(SubscriptionState subState, AssemblyManifest deployment)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

川水往事 2024-12-24 01:29:56

我发现问题出在哪里了。我们有两台负载平衡服务器,其中一台具有应用程序的早期版本。用户在服务器之间来回切换,有时会得到错误的版本。

I found out what the problem was. We have two load balanced servers and one of them had the prior version of the application. The users were bouncing between servers and sometimes getting the wrong version.

彩虹直至黑白 2024-12-24 01:29:56

您需要查看此处并确保您的自动更新选项配置正确。

  • 您可能尚未将应用程序的版本更新为高于已部署的版本。
  • 或者您的应用程序版本不大于或等于您为应用程序设置的最低版本(如果您已设置)。

You'll want to look here and make sure that your Automatic Update Options are configured correctly.

  • Chances are that you haven't updated your Application's version to be higher than what has already been deployed.
  • Or that your application's version isn't greater than or equal to a Minimum Version that you've set for the application (if you've set that).
回忆凄美了谁 2024-12-24 01:29:56

我遇到了相同的错误消息,但根本原因却截然不同。由于搜索引擎都指向这个问题(如果我将我的变体作为问题发布,它可能会被标记为“重复”),这是我的问题版本的答案:

我有一个项目,我想部署多个次。 (一个用于生产,另一个用于测试。因此,我创建了多个链接到相同源代码的项目文件。然后在编译期间使用配置设置修改可执行文件,以链接到测试或生产数据库。)发生的情况是不同的安装变得混乱与彼此。我找到了两个解决方案。 1)每个项目使用不同的证书。 (或者一个项目没有证书,另一个项目有证书)。 2) 使两个项目之间的应用程序程序集名称不同。

我希望这对某人有用。

I ran into the same error message, but from a very different root cause. Since the search engines all point to this question (and if I post my variant as a question it will probably be tagged a "duplicate") here's the answer to my version of the problem:

I had a single project that I wanted to deploy multiple times. (One for production, another for test. So I created multiple project files linked to the same source code. Then used configuration settings to modify the executables during compile to link up to test or production databases.) What happened is the different installs became confused with each other. I found two solutions. 1) Use a different certificate for each project. (or one project with no certificate and the other with a certificate). 2) Make the application assembly name different between the two projects.

I hope this is useful to someone.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文