Edit - Stack Overflow

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Rev

@Asad - I don't see that option; I do see "Step over properties and operators (Managed only)" but am I correct in understanding that enabling this will just step over the properties which isn't the desired result? I am not "stepping" when the debugger evaluates the property and changes it's value. Forgive me if I misunderstood what you were trying to say.
– dugas
Commented Feb 22, 2010 at 3:13
Oh man, sorry, you need to "UnCheck" this option. Debugger will then Step Into Properties. Have modified answered.
– Asad
Commented Feb 22, 2010 at 3:14
I had that option unchecked when I posted the question. I do not want to step, I want to catch a breakpoint in the property's get accessor. Thanks for the input though.
– dugas
Commented Feb 22, 2010 at 3:24
I rolled back your edit of the title. I am not asking how to step into properties when debugging.
– dugas
Commented Feb 22, 2010 at 3:30

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »

Collectives™ on Stack Overflow