| Reporter |
Sven Heitmann (sheitmann)
|
|---|---|
| Created | Jan 12, 2012 4:35:13 PM |
| Updated | Jan 16, 2012 9:09:49 PM |
| Resolved | Jan 16, 2012 4:11:12 PM |
| Priority | Normal |
| Type | Bug |
| Fix versions | Next |
| State | Fixed |
| Assignee | Evgeny Pasynkov (pasynkov) |
| Subsystem | Code Analysis |
| Affected versions | 6.1.1 |
| Fixed in build | 6.5.1.2465 |
Hi.
First it is important to note that this issue occurs only if I activate "Assume entity value can be null: When entity doesn't have explicit NOtNull attribute".
We switched to it as it helps us much more to find code issues.
Ok now to the issue itself.
Please find attached 2 screenshots.
The first one shows the error when I use "string.IsNullOrEmpty" and the second one that there is no error when I use "String.IsNullOrEmpty".
Kind regards,
Sven
First it is important to note that this issue occurs only if I activate "Assume entity value can be null: When entity doesn't have explicit NOtNull attribute".
We switched to it as it helps us much more to find code issues.
Ok now to the issue itself.
Please find attached 2 screenshots.
The first one shows the error when I use "string.IsNullOrEmpty" and the second one that there is no error when I use "String.IsNullOrEmpty".
Kind regards,
Sven