.NET Tip: Comparing Strings Safely Seattle WA

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

InBios International
(206) 344-5821
562 First Avenue S., Ste. 600
Seattle, WA
MITS
(206) 789-8313
701 5th Ave.,
Seattle, WA
TA Netgables Pvt Ltd
1 206 623 0910
216 First Avenue South,
Seattle,, WA
Control Systems PNW, Inc.
(206) 344-5929
900 4th Ave.,
Seattle, WA
Benaroya Research Institute at Virginia Mason
(206) 341-1313
1201 9th Ave.
Seattle, WA
Advanced Computer Solutions Ltd.
(206) 624-7854
500 Union St.,
Seattle, WA
Envision Telephony, Inc.
(206) 621-9384
520 Pike St.,
Seattle, WA
International Business Machines
(800) 426-4968
1200 5th Ave.,
Seattle, WA
Information Miner
(206) 652-3425
601 Union St
Seattle, WA
Onvia, Inc.
(206) 282-5170
509 Olive Way
Seattle, WA

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

InBios International

(206) 344-5821
562 First Avenue S., Ste. 600
Seattle, WA
http://www.inbios.com/

Related Local Events
Leads Group: Wired
Dates: 11/26/2009 - 11/26/2009
Location: Mud Bay Coffee
Olympia, WA
View Details

Leads Group: Wired
Dates: 12/3/2009 - 12/3/2009
Location: Mud Bay Coffee
Olympia, WA
View Details

Leads Group: Wired
Dates: 12/13/2009 - 12/13/2009
Location: Mud Bay Coffee
Olympia, WA
View Details

Leads Group: Wired
Dates: 12/24/2009 - 12/24/2009
Location: Mud Bay Coffee
Olympia, WA
View Details

Leads Group: Wired
Dates: 12/31/2009 - 12/31/2009
Location: Mud Bay Coffee
Olympia, WA
View Details