.NET Tip: Comparing Strings Safely Boston MA

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

Eze Castle Integration
(617) 217-3000
1 Federal Street, 9th Flr.
Boston, MA
Cogent Communications
(617) 482-5546
1 Summer Street, Ste. 450
Boston, MA
WordStream Internet Marketing
617-457-7870
133 Federal St.
Boston, MA
Applied Technologies, Inc.
(617) 742-2525
One Center Plaza, Ste. 240
Boston, MA
Thomas Reuters
(617) 856-2000
22 Thomson Place
Boston, MA
Starr Center @ The Schepens Eye Research Instittute
(617) 912-0100
185 Cambridge Street, 2nd Floor
Boston, MA
VIPER consulting_inc
(617)6860170
660 Massachusetts Avenue, Suite 6
Boston, MA
JCALPRO
(617) 954-2345
415 Summer Street
Boston, MA
INX Inc.
(617) 728-4440
2 Oliver Street, 10th Floor
Boston, MA
Brattle Consulting Group, Inc.
(617) 229-7210
8 Faneuil Hall Marketplace
Boston, MA

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

Eze Castle Integration

(617) 217-3000
1 Federal Street, 9th Flr.
Boston, MA

Related Local Events
Software Development Best Practices 2009
Dates: 9/21/2009 - 9/24/2009
Location: Hynes Convention Center
Boston, MA
View Details

EMBEDDED SYSTEMS CONFERENCE - BOSTON 2009
Dates: 9/21/2009 - 9/24/2009
Location: Hynes Convention Center
Boston, MA
View Details

September Networking Breakfast
Dates: 9/15/2009 - 9/15/2009
Location: Holiday Inn Boston - Somerville
Somerville, MA
View Details

September Networking Breakfast
Dates: 9/15/2009 - 9/15/2009
Location: Holiday Inn Boston - Somerville
Somerville, MA
View Details

LINUXWORLD SUMMIT 2009
Dates: 9/1/2009 - 9/1/2009
Location: IDG World Expo
Framingham, MA
View Details