Linux/Mac 上的 Silverlight
我有一个大型 winforms 应用程序，为了可移植性，我现在将其重写为 HTML5 应用程序。
有一个重要的 UI 组件，其中包含大量逻辑和 BCL 使用，很难将其重写为 HTML/JS。我想只在 SL 中拥有这个组件。
展望未来 2 年，这还能为我提供可移植性吗？
月光计划似乎陷入了困境。 苹果可能会决定制定新规则或破坏某些兼容性。
这些是真正的风险吗？或者我预计至少会拥有今天所拥有的风险？
I have a big winforms app which I now rewrite as an HTML5 app for the sake of portability.
There is an important UI component with a lot of logic and BCL usage that will be very hard to rewrite as HTML/JS. I am thinking to have this component only in SL.
Looking 2 years ahead does this still give me portability?
The moonlight project seems stuck.
Apple may decide to have new rules or break some compatability.
Are these real risks or am I expected to have at least what I have today?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
当然，这个问题没有绝对的答案，这纯粹是意见。
然而，我的建议是尽可能遵循通用标准；正如你所说 - SL 可能会弃用，Moonlight 可能不会再次更新，Apple 可能会完全放弃闪存支持。谁知道？
它们是真正的风险，但您可以进行防御性编程 - 彻底记录您的 API，考虑编写可以提供您的程序所需行为的 REST/WCF/SOAP 接口。
你的担心是对的，基本上存在风险！
There's no absolute answer to this of course, it's purely opinion.
However, my advice is to stick to general standards as much as possible; as you say - SL may deprecate, Moonlight might not update again, Apple may completely drop flash support. Who knows ?
They are real risks, but you can program defensively - document your API thoroughly, consider writing a REST/WCF/SOAP interface that can provide the behaviour your program needs.
You're right to be concerned that there are risks basically!
这不是一个容易做出的决定。例如，如果您的目标用户是 Windows 用户，那么您可以成功地使用 Silverlight。
考虑阅读这篇帖子并查看导致决策的过程（对他们来说不是 Silverlight，而是根据您的需要，因为您可能很适合）。
This is not an easy decision to take. For example, if you are targeting Windows users you can successfully go with Silverlight.
Consider reading this post and looking at the process that lead to the decision (for them it wasn't Silverlight but according to your needs, for you may suit fine).