使用浏览器外和 WCF RIA 服务在 Silverlight 4 中进行调试的问题
借助 Visual Stuido 2010，可以轻松设置 SL4 以使用浏览器外安装的应用程序进行调试。我按照 的说明进行操作这里一切似乎都设置得很好。从浏览器调试程序可以正常运行，但从 OOB 程序运行会产生不同的结果。启动后，屏幕将变为空白，然后永远挂起。我担心这可能是由于我们正在使用的某些技术造成的。
首先，会出现一个弹出窗口，因为我们正在使用 WCF RIA 服务（以前称为 .NET RIA 服务）。
“除非 silverlight 项目是从包含 RIA 服务的同一个 Web 项目托管和启动的，否则 RIA 服务将会失败。”
这似乎只是一个警告，但我怀疑这个警告可能是告诉我 RIA Services 需要将 .web 项目作为其启动项目。
我们还使用棱镜，并且该错误也具有棱镜错误的味道。 （某些内容正在加载，然后从未出现过）还有
其他人在 SL4 中的 OOB 调试方面遇到过任何问题吗？还有其他人在 SL4 中进行 OOB 调试吗？
抱歉，这太模糊了。这是一个复杂的混乱。我看到的唯一消息是斜体弹出警告。然后窗口（之前显示我们应用程序的背景）就变成空白了
With Visual stuido 2010, it's simple to set up SL4 to debug with an out-of-browser installed app. I followed the instructions from here and everything seems to set up fine. Debugging from the browser runs the program just fine, but running from the OOB program gives a different result. After starting, the screen will go blank and then hang forever. I have some concerns that it might be because of some of the technologies that we're using.
Firstly, there's a popup that happens because we're using WCF RIA Services (formerly .NET RIA Services).
"RIA Services will fail unless the silverlight project is hosted and launched from the same web project that contains the RIA Services."
This seems to just be a warning, but I have a suspicion that this warning might be telling me that RIA Services needs to have the .web project as its startup project.
We're also using prism and the error has an odor of a Prism error too. (something loading and then not ever appearing)
Has anyone else had any issues with OOB debugging in SL4? Is anyone else OOB debugging in SL4?
Sorry it's so vague. It's a complicated mess. The only message I see is the italicized popup warning. Then the window (which was previously showing the background of our application) just goes blank
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
当使用 F5 从 VS 2010 中启动应用程序时，当前调试浏览器外 Silverlight 4 应用程序存在一个已知问题。我的问题是应用程序是否在不进行调试的情况下启动（-F5 或从快捷方式运行它） ？在使用 F5 的情况下，通常会出现一个对话框，其中包含以下错误对话框“无法开始调试。发生致命错误。有关更多详细信息，请参阅 Microsoft 帮助和支持网站。 HRESULT=0x80070018”，然后应用程序似乎挂起。在这种情况下，分离允许进程继续，然后重新连接应该允许您调试该进程。
如果这完全阻塞或者您正在尝试调试启动时运行的代码（例如页面启动事件），解决此问题的一种可能方法是调用 System.Diagnostics.Debugger.Break，启动程序然后在弹出对话框时附加。
There is currently a known issue with debugging an Out of Browser Silverlight 4 application when using F5 to launch the application from within VS 2010. The question I have is whether or not the application launches without debugging (-F5 or running it from the shortcut)? In the case of using F5, a dialog typically appears with the following error dialog “Unable to start debugging. A fatal error occured. For more details, please see the Microsoft Help and Support web site. HRESULT=0x80070018” and then the application appears to hang. In this case detaching allows the process to continue and then reattaching should allow you to debug the process.
If this is completely blocking or you’re trying to debug code running at startup (like the page startup event), one possible way to get around this would be to put in a call to System.Diagnostics.Debugger.Break, start the program and then attach when dialog pops.
这可能是由于 OOBA 安装版本比您尝试调试的版本旧所致。请记住，Silverlight OOBA 不会自动将自身更新到服务器上可用的 XAP 文件的最新版本。您必须自己更新它们。如果您收到此错误，并且您已在应用程序中包含自动更新逻辑，则只需退出 VS，运行应用程序即可自动更新，然后返回并调试。
或者，您可以卸载该应用程序并重新安装。这将确保您针对最新的 VS 版本进行调试。
我在 VS 2008 和 Silverlight 3 中也遇到了同样的问题。如果我得到了它，我只是跳出并更新应用程序，然后在 VS 中重新运行它并进行完整的调试。
This can be caused by the OOBA install being older than the version you are trying to debug. Remember, Silverlight OOBAs do not automatically update themselves to the latest version of the XAP file that may be available on the server. You have to update them yourself. If you get this error and you have included the auto-update logic in your app, just bounce out of VS, run the app so it auto-updates, then go back in and debug.
Alternately, you can uninstall the app and re-install it. That will ensure you are debugging against the latest VS build.
I ran into this same issue with VS 2008 and Silverlight 3. If I got it, I just jumped out and updated the app then re-ran it in VS and had full debugging.