VS2012 debugger shows null after a null-coalescing has executed even tho it should not be null. - by DaveHanson

Status : 


Sign in
to vote
ID 779141 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 2/13/2013 7:48:21 AM
Access Restriction Public


Visual studio when using a  null-coalescing operator shows a null value for an object when debugging.   I have looked into this issue and it seems to be the fact that the  null-coalescing operator result is being inlined as function parameter via the compiler.  

Sign in to post a comment.
Posted by Dustin [MSFT] on 5/6/2013 at 2:21 PM

I'm closing this issue as there hasn't been another response. Thanks again for your feedback!

Kind Regards,
Dustin Campbell
Visual Studio Managed Languages
Posted by Dustin [MSFT] on 4/22/2013 at 8:31 AM

Thanks for contacting us about this issue. We are able to repro the problem that you described on Visual Studio 2012, but it appears to be working on recent internal builds. We believe this should work correctly for you in the next release of Visual Studio.

Kind Regards,
Dustin Campbell
Visual Studio Managed Languages
Posted by Microsoft on 2/13/2013 at 10:35 PM
Thanks for your feedback.

We are rerouting 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.
Posted by Microsoft on 2/13/2013 at 7:51 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)