Thursday, August 21, 2008 3:34 PMHi all,
I'm having an issue debugging a c# application.
It's multithreaded WPF and not doing anything particularly complex.
The problem is that I am trying to debug a function launched by a thread, but after a few steps or if I linger too long before stepping, the program runs instead of taking a step. The issue does not always occur in the same spot. Sometimes I get further, something less.
Is there a setting I need to toggle in order to stop my debugging being interrupted?
All the code I want to view is my own and available as source as a referenced project.
This is really frustrating as it is limiting the progress I can make.
Thanks in advance.
- Edited by Glacial Thursday, August 21, 2008 3:56 PM Better wording
Thursday, August 21, 2008 4:16 PMJust an addition, it doesn't seem to matter where in the code I am. It happens EVERYWHERE in the app, not just the function in question. What is this?
EDIT: More addition...
I have recently installed SP1 for visual studio 2008 nad did not have the issue prior (although I am uncertain if was always like this under SP1).
- Edited by Glacial Friday, August 22, 2008 8:58 AM Additional info
Friday, August 22, 2008 4:45 PMI have the same problem, only after the install of Service Pack 1. I have a machine without the service pack and I can step into every method with F11. After the service pack it randomly ignores F10/F11 and breakpoints and just runs. I had the same problem with thebeta of service pack 1.
Thursday, September 04, 2008 7:45 PMModeratorHi,
I believe you are running into a known issue. You can find the details at http://blogs.msdn.com/greggm/archive/2005/11/18/494648.aspx and it also points out how to disable funcevals.
- Marked As Answer by Azeem Khan - MSFTMicrosoft Employee, Moderator Thursday, September 04, 2008 7:45 PM
Wednesday, November 19, 2008 8:14 AMI am having the same issue when debugging an ASP.NET application. I'm actually stepping into a web service that is called from an external command line utility.
This is too bad, as this is a show stopper. This never happened before SP1 was installed.
Till a hotfix for this is up, how to properly uninstall SP1?