Silverlight 3 至 4 风险分析
我的公司目前使用 Silverlight 3 前端来允许用户查看来自我们的 Windows 服务的数据。 Silverlight 3 接口和服务通过 IPC 进行通信，但这是有问题的，因为 Silverlight 3 仅支持通过 HTTP 而不是 TCP 的 IPC 连接。
我们计划从 Silverlight 3 迁移到 Silverlight 4，但我们公司过去曾经历过坎坷的升级。
问题是：从 Silverlight 3 过渡到 Silverlight 4 时您遇到了哪些缺点或问题？
我正在寻找的例子有：
- Silverlight 4 中删除的大量使用的数据结构
- Silverlight 如何处理 IPC、线程或其他此类功能的根本变化
- 向后兼容性问题
- 等等。
My company currently uses a Silverlight 3 front-end to allow users to view data that comes from our Windows Services. The Silverlight 3 Interface and the Services communicate via IPC, but this is problematic as Silverlight 3 only supports IPC connections via HTTP instead of TCP.
We are planning to move from Silverlight 3 to Silverlight 4, but our company has been bitten by bumpy upgrades in the past.
The question is: What are some of the drawbacks or issues you have ran into when transitioning from Silverlight 3 to Silverlight 4?
Examples of things I'm looking for are:
- Heavily used data structures that were dropped in Silverlight 4
- Fundamental changes in how Silverlight deals with IPC, threading, or other such features
- Backwards compatibility issues
- Etc.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
Silverlight 4 有一些有价值的修复和功能。我个人还没有发现任何向后兼容性问题。
然而，Tim Heuer 在这里介绍了从 3 升级到 4 时的几个场景……
http://timheuer.com /blog/archive/2010/04/15/silverlight-4-breaking-changes-backward-compatibility.aspx
Microsoft 提供了一份完整的文档，标题为“确保您的 Silverlight 应用程序与 Silverlight 4 配合使用"。
Silverlight 4 has some valuable fixes and features in it. And I haven't found any backwards compatibility issues with it personally.
However, Tim Heuer covers a couple scenarios here when upgrading from 3 to 4...
http://timheuer.com/blog/archive/2010/04/15/silverlight-4-breaking-changes-backward-compatibility.aspx
And there's a full document from Microsoft titled, "Ensuring That Your Silverlight Applications Work with Silverlight 4".
仅一个数据点：当 SL4 仍处于测试阶段时，我们将解决方案从 SL3 升级到 SL4。我们有一个相当复杂的解决方案，其中包含六个不同的项目、双工 Web 服务以及可能 25,000 行 C#/XAML 代码。我记得，我在大约一天的时间里成功地在 SL4 上启动并运行了该项目，其中存在一些仅测试版的问题，现在应该不再是问题了。然后，我们又花了大约一周的时间来调整我们的项目，以利用 SL4 功能（例如 Net.TCP 绑定），但这并不算真正的转换时间。
Just one data point: We upgraded our solution from SL3 to SL4 when SL4 was still in beta. We had a fairly complicated solution with half a dozen different projects, duplex web services, and maybe 25,000 lines of C#/XAML code. As I recall, I managed to get the project up and running on SL4 in about a day, and that's with several issues that were beta-only, and shouldn't be a problem now. We then took about another week to tweak our project to take advantage of SL4 features (such as the Net.TCP binding), but that doesn't really count as conversion time.
史蒂夫抢先找到了我的一个链接，看来我还不能对他的帖子发表评论。因此，这是另一个带有一些额外见解的答案，因为他已经解释了在哪里可以了解更多信息。
在我测试 Silverlight 之前，我可以告诉您，向后兼容性是我们非常努力维护的。甚至在某种程度上，由于某些应用程序依赖于错误，因此错误被保留下来。
但有一些情况需要修复，因为它们是严重的错误，但如果修复它们就会破坏兼容性。使用的一件事是所谓的怪异模式，它可以在 SL4 中运行但使用 SL3 功能。这里有一篇文章对此进行了一些讨论：
http://blogs .msdn.com/b/nickkramer/archive/2010/09/11/how-does-silverlight-compatibility-work.aspx
Steve beat me to one of my links and it appears I cannot yet comment on his post. So here's another answer with some additional insight as his already explains where to learn more.
Having worked on testing Silverlight before I can tell you that backwards compatibility was something that we worked very hard on maintaining. Even to the extent that bugs were kept in as some apps depended on them.
But there were some instances that needed to be fixed as they were bad bugs but broke compatibility if they were fixed. One thing that was used was something called quirks mode, where it could be run in SL4 but use SL3 features. And here's an article that talks a bit about it:
http://blogs.msdn.com/b/nickkramer/archive/2010/09/11/how-does-silverlight-compatibility-work.aspx