{"id":14,"date":"2008-02-19T19:06:58","date_gmt":"2008-02-20T00:06:58","guid":{"rendered":"http:\/\/www.peteonsoftware.com\/?p=14"},"modified":"2024-03-02T17:05:52","modified_gmt":"2024-03-02T22:05:52","slug":"c-extension-methods","status":"publish","type":"post","link":"https:\/\/www.peteonsoftware.com\/index.php\/2008\/02\/19\/c-extension-methods\/","title":{"rendered":"C# Extension Methods"},"content":{"rendered":"

One of my favorite features of C# 3.0 is the extension method. An extension method basically allows you to add a method to a class without altering the class itself. All you need to do is declare some static methods with a “this” keyword in the parameters. .Net will then add this method on to whatever class you indicate is a parameter of the method (immediately following the “this” keyword). Then, as long as you have included the namespace in your using declarations in the code file, you are all set. Some examples would probably help. Here are some sample declarations. <\/p>\n

\r\npublic static class MyExtensions\r\n{\r\n    \/\/\/ <summary>\r\n    \/\/\/ Validates (poorly) if an email address is in\r\n    \/\/\/ the right format.\r\n    \/\/\/ <\/summary>\r\n    \/\/\/ <param name=\"address\">The email address to validate<\/param>\r\n    \/\/\/ <returns><\/returns>\r\n    public static bool IsEmailAddress(this string address)\r\n    {\r\n        \/\/ Note: A purposely short pattern.  Not suitable\r\n        \/\/ for enterprise-level validation\r\n        Regex regex = new Regex(@\"^[\\w-\\.]+@([\\w-]+\\.)+[\\w-]{2,4}$\");\r\n        return regex.IsMatch(address);\r\n    } \r\n\r\n    \/\/\/ <summary>\r\n    \/\/\/ Determines the future datetime, given the number\r\n    \/\/\/ of minutes to go forward.\r\n    \/\/\/ <\/summary>\r\n    \/\/\/ <param name=\"minutes\">Number of Minutes to Add<\/param>\r\n    \/\/\/ <returns><\/returns>\r\n    public static DateTime MinutesFromNow(this int minutes)\r\n    {\r\n        return System.DateTime.Now.AddMinutes(minutes);\r\n    } \r\n\r\n    \/\/\/ <summary>\r\n    \/\/\/ Reverses the characters in a string. \r\n    \/\/\/ This method should have been included in the base library.\r\n    \/\/\/ <\/summary>\r\n    \/\/\/ <param name=\"input\">The string to be reversed<\/param>\r\n    \/\/\/ <returns><\/returns>\r\n    public static string Reverse(this string input)\r\n    {\r\n        char[] inputArray = input.ToCharArray();\r\n        Array.Reverse(inputArray);\r\n        return new string(inputArray);\r\n    }\r\n}\r\n<\/pre>\n
You can see that I’ve created three methods and added XML comments to them (so I get intellisense on those methods later).  Looking at the Reverse method, I declare it just like a normal method, “public static string Reverse” but then in the arguments, I just add a “this” before I set the parameter.  So, instead of just “string input”, I have “this string input”.  This tells .Net to add this method as an extension on the string class.  <\/p>\n
You can see from this example that I see my Reverse method in a string’s intellisense as well as my comments for the method.
\n\"Example<\/p>\n
My total code to use each of my extension methods listed above is as follows.<\/p>\n
\r\nstatic void Main()\r\n{\r\n    Console.WriteLine(\"Reversed String: {0}\", \"PeteOnSoftwareRules!\".Reverse());\r\n    Console.WriteLine(\"Now: {0}\", System.DateTime.Now);\r\n    Console.WriteLine(\"In 20 Mins: {0}\", 20.MinutesFromNow());\r\n    Console.WriteLine(\"president@whitehouse.gov: {0}\", \"president@whitehouse.gov\".IsEmailAddress());\r\n    Console.WriteLine(\"NotAnEmailAddress: {0}\", \"NotAnEmailAddress\".IsEmailAddress());\r\n}\r\n<\/pre>\n
When I run the code, I get the following results.
\n\"Example<\/p>\n
Good so far, but for now it seems like I am just changing how you would write some validation methods.  Instead of IsEmailAddress(“a@b.com”), I am suggesting you write “a@b.com”.IsEmailAddress().  That is true so far.  You could also create your own type that inherits from string and add a method, but then everyone else would have to use your type instead of the built-in .Net type.  That’s not good at all.  Additionally, extension methods add value by solving another problem.<\/p>\n
Sometimes, you have to work with a framework or some third party class that has been sealed.  I have for you the following example.  It isn’t super useful, but concise, and will show my point \ud83d\ude09<\/p>\n
\r\npublic sealed class CannotInheritAndExtend\r\n{\r\n    public string FirstName = string.Empty;\r\n    public string LastName = string.Empty; \r\n\r\n    public void PrintFirstName()\r\n    {\r\n        Console.WriteLine(\"First Name: {0}\", this.FirstName);\r\n    }\r\n}\r\n<\/pre>\n
I really need this class to write out the last name, also.  With this example, it is impossible to say “public class WillInheritAndExtend : CannotInheritAndExtend” and then just add my own method.  Go ahead and try.  You will get a beautiful compiler error.  What you can do, however, is the following:<\/p>\n
\r\npublic static void PrintLastName(this CannotInheritAndExtend input)\r\n {\r\n    Console.WriteLine(\"Last Name: {0}\", input.LastName);\r\n }\r\n<\/pre>\n
Now my method is included in intellisense for the original class.
\n\"Intellisense<\/p>\n
So, now I can have this code<\/p>\n
\r\nCannotInheritAndExtend a = new CannotInheritAndExtend();\r\na.FirstName = \"pete\";\r\na.LastName = \"shearer\";\r\na.PrintFirstName();\r\na.PrintLastName();\r\n<\/pre>\n
that produces the desired output.
\n\"Results<\/p>\n
As you can see, extension methods are really very helpful.  They allow you to keep original types intact, but extend functionality onto them.  I hope you find them as useful and cool as I do.<\/p>\n","protected":false},"excerpt":{"rendered":"
One of my favorite features of C# 3.0 is the extension method. An extension method basically allows you to add a method to a class without altering the class itself. All you need to do …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15],"tags":[89,19],"class_list":["post-14","post","type-post","status-publish","format-standard","hentry","category-code-tips","tag-code-tips","tag-extension-methods"],"_links":{"self":[{"href":"https:\/\/www.peteonsoftware.com\/index.php\/wp-json\/wp\/v2\/posts\/14","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.peteonsoftware.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.peteonsoftware.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.peteonsoftware.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.peteonsoftware.com\/index.php\/wp-json\/wp\/v2\/comments?post=14"}],"version-history":[{"count":0,"href":"https:\/\/www.peteonsoftware.com\/index.php\/wp-json\/wp\/v2\/posts\/14\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.peteonsoftware.com\/index.php\/wp-json\/wp\/v2\/media?parent=14"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.peteonsoftware.com\/index.php\/wp-json\/wp\/v2\/categories?post=14"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.peteonsoftware.com\/index.php\/wp-json\/wp\/v2\/tags?post=14"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}