Silverlight 稳定性
我不知道是否有人可以就此提出建议。我们已经编写并实现了 LOB Silverlight 3 应用程序 - 目前正在客户站点上进行测试。
我们遇到过这样的问题：在现场的几台机器上，浏览器随机崩溃。这些机器运行 Windows XP SP3 - 浏览器是 Firefox。
我们怀疑这可能是因为这些机器的浏览器似乎不可靠，因为它们安装了一些插件等，建议的解决方案是在浏览器外模式下实现应用程序。
我想知道的是，当 Silverlight 3 应用程序在浏览器之外运行时，它是否仍然依赖于后台的特定浏览器......或者如果浏览器由于插件而“不稳定”，这会解决我们的问题吗？
I don't know if anyone can advise about this one. We have written and implemented a LOB Silverlight 3 application - which we are currently testing at a clients site.
We have come across the problem, where on a few of the machines on site the browsers crash randomly. The machines run Windows XP SP3 - the browser is Firefox.
We suspect that it may be because these machines browser's seems to be unreliable as they had some plugins installed etc. and a suggested solution was to implement the application in the out of browser mode.
What I want to know is, when a Silverlight 3 Application is running out of browser, is it still relying on a specific browser in the background... or would this solve our problem if the browser is "unstable" because of plugins?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我正在努力寻找证据，但我很确定我记得读过浏览器外使用 Internet Explorer 引擎。
编辑
这篇文章 强化我的记忆。
并且本文也意味着相同，如果您转到“检测网络连接和浏览器外状态”部分并阅读最后一段，以“您可以使用本地消息传递在...之间进行通信”。
I'm struggling for evidence but I'm pretty sure I remember reading that out-of-browser uses the Internet Explorer engine.
EDIT
This post reinforces my memory.
And this article implies the same, if you go to the section "Detecting Network Connectivity and Out-of-Browser Status" and read the final para, beginning "You can use local messaging to communicate between...".
不会。Silverlight OOB 应用程序与安装时运行该应用程序的浏览器之间没有任何连接。一旦作为 OOB 应用程序运行，Silverlight 将使用其自己的 ClientHTTP 堆栈，而不再依赖于浏览器 HTTP 堆栈。
假设不稳定是 Firefox 扩展造成的，那么在 OOB 中运行应用程序可能会有所帮助。但请记住，浏览器的 HTTP 堆栈可能会更高效，并且您会失去自动 cookie 处理功能。
No. There is no connection between a Silverlight OOB application and the browser in which it was running when installed. Once running as an OOB application Silverlight uses its own ClientHTTP stack and no longer depends on the Browser HTTP stack.
Assuming the instability is a result of Firefox extensions then running the app in OOB may help. Bear in mind though, that the browser's HTTP stack is likely to be more efficient and you loose automatic cookie handling.
如果 silverlight 在浏览器内崩溃，那么 silverlight 中只有少数部分实际上依赖于浏览器正确运行，例如对 Web 服务的调用必须通过浏览器 HTTP 外观，可能由于滞后而导致来自服务器的太多响应排队UI 会导致崩溃，因为太多响应试图立即触发 UI 更改事件，我知道这不太可能，但这是一个想法。
生命周期管理也由浏览器处理，插件可能会尝试回收 silverlight 进程并重新启动它。
尝试使用此调试实用程序 silverlight间谍 来找出问题的根源
If silverlight is crashing within the browser then there's only a few parts of silverlight that actually rely on the browser operating correctly, such as calls to webservices must go through the browsers HTTP facade, maybe too many responses from the server are queued due to a lagging UI which results in a crash since too many responses are trying to fire events for UI changes at once, unlikely yes i know, but its an idea.
Lifetime management is also handled by the browser, a plugin may be trying to recycle the silverlight process and restart it.
Try using this debugging utility, silverlight spy to get to the bottom of the problem