75

I am getting the following error message while running .net 3.5 applciation

Your step-into request resulted in an automatic step-over of a property or operator.

This behavior can be overridden in the context menu for the line being executed by choosing 'Step Into Specific' or by unchecking the option 'Step over properties and operators'.

Do you want continue being notified when an automatic step-over happens?

What does this error message mean?

Merin Nakarmi
  • 3,148
  • 3
  • 35
  • 42
Bala
  • 1,386
  • 1
  • 14
  • 27

9 Answers9

58

VS2017, VS2019 and VS2022:

Tools > Options > Debugging > Uncheck "Step over properties and operators > (Managed only)".

radbyx
  • 9,352
  • 21
  • 84
  • 127
51

It is not an error message as such. The IDE is telling you that tracing for some of your code is being skipped during debugging due to the current settings. If you want to be able to trace into the code, change the settings as described in the message.

You can change this behavior by going to: Tools -> Option -> Debugging.

Brian Rasmussen
  • 114,645
  • 34
  • 221
  • 317
  • 4
    i think its useful to have it enabled.. any ideas on how to just stop the confirmation popup from showing up all the time? – Sonic Soul May 16 '17 at 20:44
  • 1
    @SonicSoul it's right in the message box - "Do you want continue being notified when an automatic step-over happens?" Click no – Mike G Jan 29 '20 at 16:07
  • Is *[this](https://stackoverflow.com/questions/2672996/your-step-into-request-resulted-in-an-automatic-step-over-of-a-property-or-opera/60531199#60531199)* the reason – Irf Mar 04 '20 at 17:16
33

The setting for this in VS2010 is under: Tools -> Option -> Debugging (near the middle)

Jess
  • 2,991
  • 3
  • 27
  • 40
20

To be more specific: the option to enable in Visual Studio 2010 is:

Tools->Options->Debugging->General->Enable property evaluation and other implicit function calls

Jay Baxter
  • 416
  • 5
  • 10
15

As answered by other people this is an informational message from Visual Studio telling you that it could have stepped into a line of code but rather stepped over it due to current dev environment settings.

There are three ways to change this behaviour in VS2012:

  • Change the settings: Tools->Options->Debugging->General->Step over properties and operators OR
  • Right click on the line of code to get the context menu. Then untick: Step over properties and operators OR
  • Select 'Step into Specific' in the right click context menu which will ask you which specific function you would like to step into. It will list all the properties/functions involved in the current source line.
Caz
  • 444
  • 6
  • 7
9

In Visual Studio 2013: right click on the line that caused the message to pop-up. This will bring up the context menu. Uncheck the option: Step over properties and operators.

9

Other posts have the correct answer, which state that you can change the option in Tools > Options > Debugging > Step over properties and operators (Managed only) in Visual Studio. I wanted to add an image from the Options dialog for those who are visual. Uncheck the property if you want to perform Step Into (F11) without automatic Step Over (F10). enter image description here

iCode
  • 1,254
  • 1
  • 13
  • 16
4

The reason that we get this prompt is:
that we may have created properties or operators in our classes, and when, during debugging, we reach that line of code, it is stepped over (like the effect of F10 ) instead of stepping into ( the actual effect of F11 )

e.g., this line of code,

enter image description here

having pressed F11 here, resulted into effect of pressing F10 enter image description here
So Visual Studio notifies us..and gives this beautiful, well illustrated message, which I could only understand when I read the following blogpost

Credits: AutoStepOver a blog post

Irf
  • 4,285
  • 3
  • 36
  • 49
1

The other answers are sufficient for turning the feature on or off. But what they lack is the insight as to why one would want to do one or the other.

For beginning C# programmers, their property method is a simple {get,set}. Since this code is not worth viewing, we check the box "Step over properties...".

However, when your property settings become more interesting, you may want to step into the property method to ensure it's behavior is correct. Once you tell the IDE "Don't bother me any more", then later when your "step into" fails for a complex property method, now it's your fault.

My recommendation would be either to remember how to switch the option on and off for future debugging sessions or uncheck the "Step over..." setting and learn to toggle between F11 and F10 as appropriate.

Another option is never to use "step into". Just set a breakpoint in the method/property/operator you want to debug and click the step (F10). This way you step into only the methods you are debugging.

Adrian Mole
  • 49,934
  • 160
  • 51
  • 83
Guest 1
  • 11
  • 1