There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
Improve handling of failed assertions
Looking at the WER reports, it seems that some of our debug assertions are being hit (though not having any effect in release builds). Typically, a NullReferenceException is then thrown, and since it's coming through WER it must be bringing down VS completely.
We should add proper handling after assertions (where possible) to avoid users having VS crash.