自动升级是企业 Web 应用程序所期望的现实功能吗？
我所做的大部分工作都是与企业 Web 应用程序有关。 这些项目有大量预算、较长时间（3-12 个月）和大量定制。 因为作为开发人员，我们一直在宣扬将 Web 作为下一个桌面操作系统的想法，因此客户开始期望在这个“新操作系统”上运行的软件与桌面上运行的软件具有相同的反应。 这包括易于管理的自动升级。 换句话说，“有可用更新。您想升级吗？” 这是一个现实的期望吗？ 任何人都可以根据尝试实现此功能的经验来谈谈吗？
Most of the work I do is with what could be considered enterprise Web applications. These projects have large budgets, longer timelines (from 3-12 months), and heavy customizations. Because as developers we have been touting the idea of the Web as the next desktop OS, customers are coming to expect the software running on this "new OS" to react the same as on the desktop. That includes easy to manage automatic upgrades. In other words, "An update is available. Do you want to upgrade?" Is this even a realistic expectation? Can anyone speak from experience on trying to implement this feature?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
在我的公司，我们拥有数千个席位的企业安装。 如果我们实施自动升级，我们的客户就会叛变！
大型装置存在一些不适用于小型装置的特殊问题。 例如，对于 2000 个用户（我们可以说，并不是所有用户都是最熟练的工具用户），工具培训是一件大事：培训时间、内部演示、内部流程文档等。新功能或 UI 更改没有机会了解它如何适合他们的流程，因此他们的内部最佳实践是什么以及如何将其传达给用户。
此外，当应用程序出现故障时，内部 IT 团队也要承担责任。 因此，他们需要时间在测试区域安装新版本，进行完善，并在周六做好准备后进行部署。
我可以看到使小补丁更易于安装的价值，特别是当补丁只是用于错误修复而不是任何需要重新培训的内容时，并且如果管理员仍然对安装时间有最终决定权。 但即便如此，我相信也没有人提出过这样的要求！ 无论是因为他们不想要它，还是因为他们被训练不期望它，这似乎都不值得。
At my company we have enterprise installations ranging into the thousands of seats. If we implemented an auto-upgrade, our customers would mutiny!
Large installations have peculiar issues that don't apply to small ones. For example, with 2000 users (not all of whom are, let us say, the most sophisticated of tool users), tool-training is a big deal: training time, internal demos, internal process documents, etc.. They cannot unleash a new feature or UI change without a chance to understand how it fits in their process and therefore what their internal best practices are and how to communicate that to their users.
Also when applications fail, it's the internal IT team who are responsible. Therefore, they want time to install a new version in a test area, beat it up, and deploy on a Saturday only when they're good and ready.
I can see the value in making minor patches more easy to install, particularly when the patch is just for a bug-fix and not for anything that would require retraining, and if the admins still get final say over when it's installed. But even then, I don't believe anyone has ever asked for this! Whether because they don't want it or they are trained to not expect it, it doesn't seem worth it.
嗯，这实际上取决于您的业务模式，但对于许多应用程序来说，SaaS 模式最终可能会困扰您。 它对于很多事情来说都很棒，但是对于一些较大的应用程序，用户不会预先投入大量资金，并且可能会在赚钱之前转向其他应用程序。
请参阅
http://news.zdnet.com/2424-9595_22-218408.html
和此处
http://www.25hoursaday.com/weblog/ 2008/07/21/SoftwareAsAServiceWhenYourBusinessModelBecomesAParadox.aspx
了解更多信息
Well, it really depends on your business model but for a lot of applications the SaaS model can end up biting you. It's great for a lot of things but for some larger applications the users are not investing as significant amount up front and could possibly move to something else before you've made any money.
See
http://news.zdnet.com/2424-9595_22-218408.html
and here
http://www.25hoursaday.com/weblog/2008/07/21/SoftwareAsAServiceWhenYourBusinessModelBecomesAParadox.aspx
for more information
将应用程序实现为 Web 应用程序的主要原因之一是您可以免费获得自动升级。 为什么网络应用程序会提示用户升级？
对于Windows应用程序，“更新可用，您要升级吗？” Microsoft 使用 ClickOnce 提供了该功能，我已在企业环境中成功使用了该功能 - 虽然存在一些问题，但在大多数情况下，它是管理 Windows 应用程序自动部署和升级的好方法。
对于移动应用程序，您还可以实现自动升级，尽管这有点棘手。
无论如何，要从广义上回答您的问题，我不知道是否期望所有企业应用程序都应该使升级变得容易，但从 IT 支持的角度来看，将它们构建为允许轻松升级肯定是值得的。升级。
One of the primary reasons to implement an application as a web application is that you get automatic upgrades for free. Why would users be getting prompted for upgrades on a web app?
For Windows applications, the "update is available, do you want to upgrade?" functionality is provided by Microsoft using ClickOnce, which I have used in an enterprise environment successfully -- there are a few gotchas but for the most part it is a good way to manage automatic deployment and upgrade of Windows apps.
For mobile apps, you can also implement auto-upgrades, although it is a little trickier.
In any case, to answer your question in a broad sense, I don't know if it is expected that all enterprise apps should make upgrading easy, but it certainly is worth the money from an IT support standpoint to architect them to allow for easy upgrading.
如果您提供托管解决方案，我不会打扰。 让升级悄无声息地进行（也许会通知您已执行此操作）。 如果您要销售托管在其服务器上的应用程序，请让升级决定由单个所有者做出，而不是由该应用程序的每个用户做出。
If you're providing a hosted solution, I wouldn't bother. Let the upgrade happen silently (perhaps with a notice that you did it). If you're selling an application that's hosted on their servers, let the upgrade decision be made by a single owner, not every user of the app.