Home Dashboard Directory Help
Search

Unable to set breakpoint to C# automatic property by Marek Safar


Status: 

Closed
 as Won't Fix Help for as Won't Fix


23
0
Sign in
to vote
Type: Bug
ID: 408762
Opened: 1/30/2009 7:25:09 AM
Access Restriction: Public
1
Workaround(s)
view
18
User(s) can reproduce this bug

Description

Unable to set breakpoint to C# automatic property
Details
Sign in to post a comment.
Posted by davisnw on 2/11/2011 at 8:17 AM
Honestly? "Won't Fix"? This is a huge annoyance when debugging, and greatly decreases the utility of auto-implemented properties.
Posted by Duncan Bayne on 11/10/2010 at 10:06 PM
No data breakpoints, no auto-property breakpoints ... not helpful when trying to track down the reason a particular property is being set to a particular value. Please fix this!
Posted by firewyre on 10/19/2010 at 12:18 PM
I see this was closed as "Won't Fix" - does this mean it won't be fixed in VS2010 either? This limitation is extremely lame...
Posted by Microsoft on 2/5/2009 at 2:42 PM
Thanks for the suggestion for Visual Studio!

Unfortunately, we are starting to lock down on our feature set and won't be able to make breakpoints work there this time around. There are a set of improvements to auto-implemented properties we've examined (from supporting initializers to allowing them to be readonly), and we'll definitely keep this in mind too when planning for our next release!

Alex Turner
Program Manager
Visual C# Compiler
Posted by Microsoft on 2/1/2009 at 8:28 PM
Thanks for your feedback.

We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team
Sign in to post a workaround.
Posted by Duncan Bayne on 11/10/2010 at 10:07 PM
Seems obvious ... but you can always convert the auto-property to a property with a backing field; ReSharper has a transform for this. Then set the breakpoint on the setter and / or getter. Lame.