I have a unit test that calls a method on an object passing in a string.
One of the first things that the method being called does is to check the string for null or
This is the first time I have come across this issue.
The way we stepped round it for now is to add the following on the back of the IF statement.
#if DEBUG else { // A hack to fix the debugger issue on the IsNullOrEmpty statement above. } #endif