找到两个方法:
1.
after upgrading ReSharper from 5.0 to 5.1.1 yesterday, I can't reproduce the issue any more right now. If it happens again, I will create a video file.2. Have this same exact problem myself. Found that a Workaround is checking the "Enable unmanaged code debugging" checkbox. After doing that the error message no longer pops up everytime I attempted to debug. Also I only started to recieve this problem after I installed SP1 for Visual Studios 2010 and the four updates it installed after that. Which was also strange because the 4 updates came out in September (before the service pack) but didn't show up to install as updates until after installing the service pack.来自:
http://connect.microsoft.com/VisualStudio/feedback/details/624213/attaching-the-proteusdebugengine-debugger-to-process-qtagent32-exe-on-machine-failed-invalid-pointer
1.
after upgrading ReSharper from 5.0 to 5.1.1 yesterday, I can't reproduce the issue any more right now. If it happens again, I will create a video file.2. Have this same exact problem myself. Found that a Workaround is checking the "Enable unmanaged code debugging" checkbox. After doing that the error message no longer pops up everytime I attempted to debug. Also I only started to recieve this problem after I installed SP1 for Visual Studios 2010 and the four updates it installed after that. Which was also strange because the 4 updates came out in September (before the service pack) but didn't show up to install as updates until after installing the service pack.来自:
http://connect.microsoft.com/VisualStudio/feedback/details/624213/attaching-the-proteusdebugengine-debugger-to-process-qtagent32-exe-on-machine-failed-invalid-pointer
open Command Prompt as Administrator and execute below command(s):
regsvr32 "C:\Program Files\Internet Explorer\ieproxy.dll"
for 64 bit windows, also try this:
regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll"
OR Also:
Running the following in the Visual Studio Command Prompt (2010) Execute Command:
devenv /resetskippkgs