.NET Tip: Type Casting and Comparison Using "as" and "is" Dallas TX

Use some of the language's lesser known features for safe type casting and comparison.

Local Companies

Videotex Systems
972 231 9200 x124
10255 Miller Road
Dallas, TX
elKore Inc
1-877-355-6731
12225 Greenville Avenue
Dallas, TX
Information Processing Corporation
972-404-9244
13747 Montfort, Suite 300
Dallas, TX
Maxtrus Micro
(800) 910-2380
4781 Snow Dr
Mesquite, TX
Spatial Data Inc.
972-791-0911
4545 Fuller Drive
Irving, TX
C. Pitman Baker & Associates
972-579-1642 X 227
1431 Greenway Dr.
Irving, TX
In2 Solutions Inc
(972) 494-7400
3534 W Walnut St
Garland, TX
P O Express Inc
(972) 272-0603
3717 Burning Tree Ln
Garland, TX
Sixred, Inc.
(972) 365-3437
15950 North Dallas Parkway
Dallas, TX
Freeman Software
(972) 840-1119
506 Valencia Dr
Garland, TX

provided by: 
Originally published at Internet.com


You are probably used to using C-style casts. Look at an example starting with C-style casts and see how using "as" and "is" can help your code. A common situation I run into is working with controls in an ASP.NET DataGrid. Suppose I need to work with the DataGridItem that is the parent of one of the controls in the grid. Using C-style type casting, I would do something like this: // C-style try { DataGridItem item = (DataGridItem)mycontrol.Parent; if (item.GetType().ToString() == "DataGridItem") { // Do something interesting here } } catch (InvalidCastException ex) { }

Although this method works, there is a much cleaner way. First, I'll address the type cast and exception handling using "as". With "as", there is no need to check for exceptions Because it will either return the object as the requested type or it will return null. You then can check the value against null to see whether the type conversion was successful. // Using As DataGridItem item = mycontrol.Parent as DataGridItem; if (item != null) { // Do something interesting here }

This code is much more concise and explicit than when using C-style type casting. Adding the use of "is" in the comparison makes this code more readable and is slightly more efficient than the comparison to null. The end result looks like this: // Using As and Is DataGridItem item = mycontrol.Parent as DataGridItem; if (item is DataGridItem) { // Do something interesting here }

Compare this with the original version using C-style type casting. I think that you will agree the version using "as" and "is" is easier to understand and maintain because there is no need to worry about invalid cast exceptions.

About the Author

Jay Miller is a Software Engineer with Electronic Tracking Systems, a company dedicated to robbery prevention, apprehension, and recovery based in Carrollton, Texas. Jay has been working with .NET since the release of the first beta and is co-author of Learn Microsoft Visual Basic.Net In a Weekend. Jay can be reached via email at jmiller@sm-ets.com.

Author: Jay Miller

Read article at Internet.com site

Featured Local Company

Videotex Systems

972 231 9200 x124
10255 Miller Road
Dallas, TX
http://www.videotexsystems.com/

Related Local Events
Unconventional Gas Conference & Exhibition
Dates: 9/29/2009 - 10/1/2009
Location: Fort Worth Convention Center
Fort Worth, TX
View Details

Tech Titans Fast Tech Awards Gala
Dates: 8/28/2009 - 8/28/2009
Location: Renaissance Dallas Richardson Hotel
Richardson, TX
View Details

AHS International 65th Annual Forum and Technology Display
Dates: 5/27/2009 - 5/29/2009
Location: Gaylord Texan Resort & Convention Center
Grapevine, TX
View Details