This warning indicates that ReSharper Null Reference analisys failed to process the method because analysis data exceeded empirical limit. Usually this is a sign that a method has too complex control flow and/or too much data operated. We will apreciate if you post the method body that raised this warning. The text of the warning will be discarded or replaced with a more informative one (? "Method is too complex. Try refactoring it.") in the release.
In build 300 ReSharper for VS2005 has found that one of my method has warning "control flow complexity is overflow"
Thank you for your answer. I do not thonk that this method is a good example of the proper C# programming style, but you can try it like a source for the warning generation
This warning indicates that ReSharper Null Reference analisys failed to process
the method because analysis data exceeded empirical limit. Usually this is
a sign that a method has too complex control flow and/or too much data operated.
We will apreciate if you post the method body that raised this warning.
The text of the warning will be discarded or replaced with a more informative
one (? "Method is too complex. Try refactoring it.") in the release.
Best regards,
Andrey Simanovsky
Hi Andrey
Thank you for your answer. I do not thonk that this method is a good example of the proper C# programming style, but you can try it like a source for the warning generation
Regards
Sergey
Attachment(s):
problematic_method.cs
"Sergey Vasiliev" <no_reply@jetbrains.com> wrote in message
news:11414995.1163092034351.JavaMail.itn@is.intellij.net...
That's an understatement! A nine page method!
John
I think I improved the metrcics by opening it on a big screen with a small font. I got it to less than 2 pages long!
Tee hee