3 votesRS commented
To clarify, you tried creating your own snippet and... is it missing a feature? If so, what feature are you actually requesting for?
By your comment, it seems that you are not aware that you can create your own snippets, so I just wanted to clarify that.
Thank you for using Visual Studio and for your commitment to improving it. We are actively evaluating whether we will be able to bring this suggestion into the product for .NET developers for the System.NullReferenceException in a future release.
We have recently made an improvement, similar to this suggestion, for debugging C++ Access Violations in Visual Studio 2015 Update 1.
Read about it here: http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/29/improvement-to-debugging-c-access-violations-in-visual-studio-2015-update-1.aspx
We encourage you to continue to comment on and vote for this UserVoice item to share any additional feedback that you have for this suggestion.
Visual Studio DiagnosticsRS supported this idea ·
4,931 votesRS commented
Just my two cents but this seems like a weird request; one, I just hope, it's not seen as a priority.
The core reason behind this appears to be laziness but, being lazy myself, I believe that there are multiple (and way simpler) approaches to this "problem"; e.g., snippets, T4, the ingenious NonNullable struct, etc. It seems everyone agrees that no suggested solution would be (100%) "safe", so I'm actually amazed of how much energy can go into this.
P.S. I'm a little surprised by the... "simplicity" of this forum, including the order of the posts --very unfriendly for reading a thread.