.NET Tip: Comparing Strings Safely San Antonio 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

SoloComputers.com
915-204-8163
7903 Pinebrook Dr.
San Antonio, TX
Q A Solutions Inc
(210) 348-7131
1603 Babcock Rd Ste 254
San Antonio, TX
Frontline Systems Inc
(210) 822-0494
8610 Broadway St Ste 280
San Antonio, TX
Petrich Consulting
(210) 657-3851
5123 Sirretta Dr
San Antonio, TX
Ccmcs Inc
(210) 495-8812
14607 San Pedro Ave
San Antonio, TX
Ocasio Computer Consulting
(210) 545-5539
San Antonio, TX
Tech Now Computer Training
(210) 732-1242
4243 E Piedras Dr Ste 250
San Antonio, TX
Ynl Consulting
(210) 340-0098
7550 W Ih 10
San Antonio, TX
Alamo City Computer Consultants
(210) 492-1566
13138 Hunters Brook St
San Antonio, TX
Champion Computers Inc
(210) 647-4999
5720 Bandera Rd
San Antonio, 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

SoloComputers.com

915-204-8163
7903 Pinebrook Dr.
San Antonio, TX
http://SoloComputers.com

Related Local Event
2009 IEEE International Conference on Systems, Man and Cybernetics - SMC
Dates: 10/11/2009 - 10/14/2009
Location: Hyatt Regency Riverwalk
San Antonio, TX
View Details