| Reporter |
Andrey Simukov (Andrey.Simukov)
|
|---|---|
| Created | Feb 19, 2018 8:30:48 PM |
| Updated | Apr 12, 2018 5:17:41 PM |
| Subsystem | Debugger features |
| Assignee | Tatyana Lunegova (lunega) |
| Priority | Normal |
| State | Waiting for Info |
| Type | Bug |
| Fix version | No Fix versions |
| Affected versions | 2017.3.2 |
| Fixed In Version ReSharper | Undefined |
| VsVersion | All Versions |
When running for example a LinqToSql statement the feature "Show current line expression values in editor" throws a Null Exception error. The workaround for us right now is to turn off that feature and everything works fine.
Here is a screenshot, when we run this code with ”Show current line expression values in editor” turned off, everything works fine.
I had to anonymized the code a little, I hope you see what you need to see anyway. It is a simple where x.id = id and some null checking and finally a Contains expression.
Here is a screenshot, when we run this code with ”Show current line expression values in editor” turned off, everything works fine.
I had to anonymized the code a little, I hope you see what you need to see anyway. It is a simple where x.id = id and some null checking and finally a Contains expression.