无法确定应用程序身份调用?如何追踪? [英] Unable to determine application identity call? How to track down?

问题描述

我正在制作Windows Phone 8应用程序，在Blender和VS的设计器视图中，出现无法确定应用程序身份调用"错误，是一个对话框.

I am making a windows phone 8 application and in the designer view in both blend and VS I get "Unable to determine application identity call" error as a dialog box.

根据我在堆栈上所读的内容，这可能是因为隔离存储正在运行并且设计人员无法处理它.

From what I read on stack this is propably because of the Isolated Storage is getting run and the designer can't handle it.

我想知道是否可以得到一些行号或发生错误的地方，而不必手动检查代码?

I am wondering is there away I can get some line numbers or something where the errors are happening instead of having to manually go through the code?

推荐答案

当您看到此消息框时，为时已晚，已捕获并处理了异常.引发异常时，您必须抓住它.在设计时做起来并不容易.

By the time you see this message box it is already too late, the exception was caught and handled. You have to catch it when the exception is raised. Which is not so easy to do at design time.

值得一试的一项技术是使用调试器来调试Visual Studio本身.再次启动它，然后使用工具+附加到进程.在进程列表中找到第一个devenv.exe并选择它.将附加到:"设置为托管(v4.5，v4.0)"，然后单击确定".让它艰难地寻找PDB(花一些时间).调试+异常，在清除"复选框中选中CLR异常.

One technique that's worth a shot is to use a debugger to debug Visual Studio itself. Start it again and use Tools + Attach to Process. Locate the first devenv.exe in the list of processes and select it. Set the Attach to: setting to "Managed (v4.5, v4.0)" and click OK. Let it trundle to find the PDBs (takes a while). Debug + Exceptions, tick the Thrown checkbox for CLR exceptions.

切换回VS的原始实例，并执行触发错误之前的所有操作.抛出异常时，第二个实例将中断.运气好的话，您会在调用堆栈"窗口中看到您的代码.如果调试器没有中断，请重复该练习，然后附加到XAML设计器XDesProc.exe.祝你好运.

Switch back to the original instance of VS and do whatever you did before to trigger the error. The 2nd instance will break in when the exception is thrown. Which some luck you'll see your code on the Call Stack window. If the debugger doesn't break then repeat the exercise but attach to XDesProc.exe, the XAML designer. Good luck with it.

这篇关于无法确定应用程序身份调用?如何追踪?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！