| Reporter |
Alex Berezoutsky (fergard)
|
|---|---|
| Created | Nov 8, 2011 5:59:41 PM |
| Updated | Dec 27, 2011 4:43:05 PM |
| Resolved | Dec 27, 2011 4:43:05 PM |
| Priority | Critical |
| Type | Bug |
| Fix versions | 6.1 |
| State | Won't fix |
| Assignee | Evgeny Pasynkov (pasynkov) |
| Subsystem | No subsystem |
| Affected versions | 6.0 |
| Fixed in build | No Fixed in build |
I attached a small sample program that illustrates the problem using the Trace.Assert() and Trace.CheckPrecondition() methods for null reference checks.
Please note that we also have an instance based trace. That is, this trace contains identical non-static Assert() and CheckPrecondition() methods.
ReSharper still complains if I use the System.Diagnostics.Trace.Assert() method.
Our preferred solution would be to provide ReSharper with a list of "Assert" methods to which the assert condition is passed as the first parameter.
ReSharper should treat the method call like an if-statement with the negated assert condition in which the remaining code is executed.
Please note that we also have an instance based trace. That is, this trace contains identical non-static Assert() and CheckPrecondition() methods.
ReSharper still complains if I use the System.Diagnostics.Trace.Assert() method.
Our preferred solution would be to provide ReSharper with a list of "Assert" methods to which the assert condition is passed as the first parameter.
ReSharper should treat the method call like an if-statement with the negated assert condition in which the remaining code is executed.