.NET Tip: Comparing Strings Safely Greensboro NC

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

L A Solutions
336-389-1707
110 E Washington St
Greensboro, NC
Software Design Inc
336-378-0900
1301 Carolina St
Greensboro, NC
Data Management Corp
336-275-1697
423 Eugene CT
Greensboro, NC
Compucon USA LLC
336-294-0604
620 Green Valley Rd
Greensboro, NC
COMPUTER TROUBLESHOOTING
336-510-7919
1400 Battleground Ave
Greensboro, NC
Spi Software Solutions
336-333-2967
2007 Yanceyville St
Greensboro, NC
Advantec Information Systems LLC
336-275-2832
2007 Yanceyville St
Greensboro, NC
D P Solutions Inc
336-854-7700
4411 W Market St
Greensboro, NC
Dalcom Consulting
336-851-1802
8 Oak Branch DR
Greensboro, NC
Engineered Software
336-299-4843
615 Guilford College RD
Greensboro, NC

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

L A Solutions

336-389-1707
110 E Washington St
Greensboro, NC
http://www.lasolutions.net