debugger - Step over property gives VS IDE specific output in debug console

[chuckries]

This appears in the debug console when stepping over a property:

Step into: Stepping over property 'MusicStore.Models.Album.get_AlbumId'.  To step into properties, go to Tools->Options->Debugging and uncheck 'Step over properties and operators (Managed only)'.
WARNING: 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 to continue being notified when an automatic step-over happens?

[sternb0t]

I'm experiencing this too. Any known workarounds?

[gregg-miskelly]

@sternb0t if you want to stop in the property - set a breakpoint, if you are just concerned about the text -- you will need to ignore it.

[sternb0t]

Thanks @gregg-miskelly but how can I set a breakpoint in a .NET core property like the ones in System.ComponentModel.DataAnnotations? Those aren't defined in my code. I was hoping justMyCode: true in launch.json would allow me to step in to wherever that code lives.

[sternb0t]

Sorry I meant to say justMyCode: false!

[gregg-miskelly]

In the short term, it is pretty difficult to step into the CoreFX. Here is what you would need to do though:

1. You need a copy of CoreFX binaries which are built using portable PDBs. @noahfalk @stephentoub do you by chance know if there is a builtin way to do this today? Would enlisting and building on Unix work?
2. You need a copy of CoreFX sources (ex: git clone https://github.com/dotnet/corefx.git and checkout the right branch). Obviously if you are building it in step 1, this goes away.
3. You need to get your project to use the CoreFX you just built.
4. If you want to step into a property, as I said, you will need to find the right source file and set a breakpoint.

[gregg-miskelly]

BTW: We have a planned feature to make this process less painful. We didn't have an issue tracking this, so I opened #373 so that you can follow progress if you are interested.

[sternb0t]

Awesome, thank you for this.

[noahfalk]

This issue has the latest status I'm aware of on CoreFX binaries producing portable PDBs:
https://github.com/dotnet/corefx/issues/5733

@dagood

[gregg-miskelly]

@chuckries I believe this is addressed with #530. Correct? If so, can you close it?

[chuckries]

@gregg-miskelly correct, this fix is in master and will be in the next release.