.NET Tip: Comparing Strings Safely Dallas TX

The .NET Framework's built-in comparison functions don't handle nulls properly. Learn a couple of functions to take care of this for you.

Local Companies

Videotex Systems
972 231 9200 x124
10255 Miller Road
Dallas, TX
elKore Inc
1-877-355-6731
12225 Greenville Avenue
Dallas, TX
Information Processing Corporation
972-404-9244
13747 Montfort, Suite 300
Dallas, TX
Maxtrus Micro
(800) 910-2380
4781 Snow Dr
Mesquite, TX
Spatial Data Inc.
972-791-0911
4545 Fuller Drive
Irving, TX
C. Pitman Baker & Associates
972-579-1642 X 227
1431 Greenway Dr.
Irving, TX
In2 Solutions Inc
(972) 494-7400
3534 W Walnut St
Garland, TX
P O Express Inc
(972) 272-0603
3717 Burning Tree Ln
Garland, TX
Sixred, Inc.
(972) 365-3437
15950 North Dallas Parkway
Dallas, TX
Freeman Software
(972) 840-1119
506 Valencia Dr
Garland, TX

provided by: 
Originally published at Internet.com


You often need to compare strings (or other data types), but sometimes a value could be null or DBNull if it's coming from the database. The .NET Framework's built-in comparison functions don't handle nulls properly, so I wrote a couple of functions to take care of this for me.

This function, and its overloaded version, compare the string value of an object and another string: private bool SafeCompare(object test, string testValue) { return SafeCompare(test, testValue, StringComparison.CurrentCultureIgnoreCase); } private bool SafeCompare(object test, string testValue, StringComparison compareSetting) { if (test != null) { if (!Convert.IsDBNull(test)) { return String.Compare(test.ToString(), testValue, compareSetting) == 0; } else return false; } else return false; }

The function first tests the object against null, then against DBNull, and then against the string in question. Any null/DBNull value will cause the function to return false. The overloaded version also allows you to default the StringComparison value, which enables you to specify case-sensitive or case-insensitive comparisons. I prefer to do a case-insensitive comparison in most cases, so that's the default value I send if that parameter is omitted.

Using this function as a model, you could easily add other overloads for non-string data types, such as doubles or integers. Here's a version for comparing two integers "safely": private bool SafeCompare(object test, integer testValue) { if (test != null) { if (!Convert.IsDBNull(test)) { return Convert.ToInt32(test) == testValue; } else return false; } else return false; }

Because the parameter types are different, you can add this overloaded version to the other two shown above. This saves a lot of duplicated code and works around the inability to deal with nulls without throwing exceptions.

About the Author

Eric Smith is the owner of Northstar Computer Systems, a Web-hosting company based in Indianapolis, Indiana. He is also a MCT and MCSD who has been developing with .NET since 2001. In addition, he has written or contributed to 12 books covering .NET, ASP, and Visual Basic. Send him your questions and feedback via e-mail at questions@techniquescentral.com.

Author: Eric Smith

Read article at Internet.com site

Featured Local Company

Videotex Systems

972 231 9200 x124
10255 Miller Road
Dallas, TX
http://www.videotexsystems.com/

Related Local Events
Unconventional Gas Conference & Exhibition
Dates: 9/29/2009 - 10/1/2009
Location: Fort Worth Convention Center
Fort Worth, TX
View Details

Tech Titans Fast Tech Awards Gala
Dates: 8/28/2009 - 8/28/2009
Location: Renaissance Dallas Richardson Hotel
Richardson, TX
View Details