You can debug a 64-bit application that is running on the local computer or on a remote computer.
To debug a 64-bit application that is running on a remote computer, seeRemote Debugging.
To debug 64-bit applications locally, Visual Studio uses a 64-bit worker process (msvsmon.exe) to perform the low-level operations that cannot be done inside of the 32-bit Visual Studio process.
Mixed-mode debugging is not supported for 64-bit processes that use .NET Frameworkversion 3.5 or earlier.
Debug a 64-bit Application
-
Create a Visual Studio solution, for example a C# console application.
-
Set the configuration to 64-bit using the Configuration Manager. For more information, seeHow to: Configure Projects to Target Platforms.
-
At this point the 64-bit version of the remote debugger (msvsmon.exe) starts. It runs as long as the solution with the 64-bit configuration is open.
-
Start debugging. You should have the same experience as with a 32-bit configuration. If you get errors, see the Troubleshooting section below.
Troubleshooting 64-bit debugging
You may see an error: “A 64-bit debugging operation is taking longer than expected.” In this case, Visual Studio has sent a request to the 64-bit version of msvsmon.exe, and it has taken a long time for the result of that request to come back.
There are two main causes for this error:
-
You have networking security software installed on your computer that has caused the networking stack to be unreliable, and it has dropped packets going over localhost. Try disabling all network security software and see if this resolves it. If so, report to your network security software vendor that the software is interfering with localhost traffic.
-
You are running into a hang or performance problem with Visual Studio. If the problem happens regularly, you can collect dumps of Visual Studio (devenv.exe) and the worker process (msvsmon.exe) and send them to Microsoft. For information about reporting a problem, seeHow to Report a Problem with Visual Studio.
最终通过总结研究,终于找到了完美的解决方案,非常简单:
1、查看Windows Firewall服务(或其它防火墙软件)是否启动,如果启动则关闭。需要注意的是,有时防火墙服务会自动启动,所以即使是设置为手动模式,也要去确认一下。
2、删除项目目录下bin和obj两个文件夹,然后重新生成项目。在重新生成时可能会提示引用的DLL错误,重新引用报错的DLL后,再次生成即可。
这时发现项目又能正常调试啦!
有些问题确实奇怪,说难真难,但解决起来却是如此简单,特此随笔以助有缘人吧。
By:行一山人Xingyihermit,Koala Studio,转载请注明出处。
作者:行一山人 出处:http://www.cnblogs.com/benbenkoala/
本文版权归作者和博客园共有,欢迎转载,但未经作者同意必须保留此段声明,且在文章页面明显位置给出原文连接,否则保留追究法律责任的权利。
转自:http://www.cnblogs.com/benbenkoala/p/5527257.html
优质内容筛选与推荐>>1、数学中的集合,群,环,域
2、hdu 1569 方格取数(2)
3、EF 映射没有主键的视图
4、IE6,7,8,9浏览器兼容性解决
5、[.NET] CErrStack 方便地管理错误或异常