Click here to Skip to main content
Click here to Skip to main content
Alternative Tip

Tagged as

Go to top

Best practices in developing ASP.NET applications

, 19 Jan 2011
Rate this:
Please Sign up or sign in to vote.
I agree with Chris...string.IsNullOrEmpty: 312 msLength: 140 ms [fastest]This is not a fair comparison.Need to compare:(string != null && string.Length !=0)with: String.IsNullOrEmpty(string)Even if the first construct is faster, there is a readability...
I agree with Chris...
 
string.IsNullOrEmpty:   312 ms
Length:                 140 ms  [fastest]
 
This is not a fair comparison.
 
Need to compare:
(string != null && string.Length !=0)
with:
String.IsNullOrEmpty(string)
Even if the first construct is faster, there is a readability factor:
 
if (!String.IsNullOrEmpty(someString)) {
//do something with someString
...
}
or:
if (someString != null && someString.Length != 0) {
//do something with someString
...
}
The second construct becomes increasingly ugly if there is more than one string to deal with.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

_impostor_
Web Developer
Australia Australia
No Biography provided

Comments and Discussions

 
GeneralHi, As u said string.IsNullOrEmpty is taking 312 ms. I real... Pinmembersendtodilip24-Jan-11 18:42 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Mobile
Web04 | 2.8.140916.1 | Last Updated 19 Jan 2011
Article Copyright 2011 by _impostor_
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid