Debugger fails to re-evaluate breakpoints when new code is executed in a transient assembly - by leppie

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


5
0
Sign in
to vote
ID 684089 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 8/14/2011 6:18:33 AM
Access Restriction Public
Moderator Decision Sent to Engineering Team for consideration

Description

The bug has been isolated from discussions at http://stackoverflow.com/questions/6937198/making-your-net-language-step-correctly-in-the-debugger.

In CLR4, when new code is generated and subsequently evaluated the debugger fails to set breakpoints correctly as it does under CLR2. 

Sign in to post a comment.
Posted by leppie on 3/26/2012 at 6:23 AM
Verified to be fixed in .NET 4.5.

Thanks.
Posted by Microsoft on 9/9/2011 at 3:06 PM
Hi leppie thanks for reporting this issue. This is indeed a bug in the v4.0 symbol reader. Unfortunately the workaround you've found is about all that can be done for now. Good news is that this has been fixed in the next major release of the .NET Framework.

-Joel
Posted by MS-Moderator10 [Feedback Moderator] on 8/14/2011 at 7:31 PM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by MS-Moderator01 on 8/14/2011 at 6:39 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)