[Mono-bugs] [Bug 362867] New rule string.IsNullOrEmpty

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Wed Mar 5 15:24:03 EST 2008


User nestor.salceda at gmail.com added comment

Néstor Salceda <nestor.salceda at gmail.com> changed:

           What    |Removed                                         |Added
                 CC|                                                |nestorsalceda at gmail.com

--- Comment #2 from Néstor Salceda <nestor.salceda at gmail.com>  2008-03-05 13:24:03 MST ---
Although isn't a bad practice with a high severity, IMHO should go in the
BadPractice category because the 2.0 profile already contains a method which
performs the check.  You are rewritting some code that already exists.

I can't access now to the FxCop page, but I remember there was a category
called "Usage" with rules for .Net specific bad/good practices (I can't ensure
now this rule was in "Usage" category, but I believe yes).  Perhaps we should
think in some seemed category or redefine the BadPractice category goals in
order to fit these new requisites.

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list