.NET Tip: Comparing Strings Safely Florence SC

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

Enterprise Solutions Inc
(843) 317-1245
2325 Prosperity Way Ste 2
Florence, SC
Pinnacle Network Solutions
(843) 662-1581
2215 W Palmetto St Ste D
Florence, SC
Taylor Data Systems
(843) 656-2084
181 E Evans St
Florence, SC
Arc Computers
(864) 543-4050
147 Belle Rive Dr
Ninety Six, SC
Advanced Technology Services
(864) 236-0436
122 Park Place Ct
Greenville, SC
DP Professionals Inc
(803) 738-0066
3741 Landmark Dr Ste B200
Columbia, SC
Uhimchuk & Associates Inc
(864) 292-3711
2506 Wade Hampton Blvd
Greenville, SC
Aac Utility Partners
(803) 736-9486
9367 Two Notch Rd
Columbia, SC
Global Pundits Inc
(803) 354-9400
2800 Bush River Rd Ste 2A
Columbia, SC
Roger's Computer Services
(803) 951-1826
235 Dooley Rd
Lexington, SC

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

Better Living Solutions

9102919929
307 Prince St
Laurinburg, NC