{"id":6191,"date":"2008-05-10T11:06:56","date_gmt":"2008-05-10T11:06:56","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2008\/05\/10\/in-praise-of-typeconverters-spread-the-love\/"},"modified":"2019-02-18T13:15:57","modified_gmt":"2019-02-18T20:15:57","slug":"in-praise-of-typeconverters-spread-the-love","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/in-praise-of-typeconverters-spread-the-love\/","title":{"rendered":"In Praise of TypeConverters – Spread the Love"},"content":{"rendered":"

I just got through reading Scott Hanselman’s blog entry:  TypeConverters: There’s not enough TypeDescripter.GetConverter<\/a> in which he referenced  Jesse Liberty’s blog entry: Did You Know That… Type Converters allow you to use property attributes in Complex Types<\/a> and decided to pile on.<\/p>\n

Developers<\/strong> – you should stop what you are doing and get TypeConverters in focus.  Here is the big picture way to think about it:  As developers, our mission in life is to make the lives of others easier by providing them the functions they need in they way they need them.  TypeConverters play a huge role in the mission.<\/p>\n

TypeConverters are one of the many the unsung heroes behind the magic of PowerShell.  Think about the code you write, think about the code your customers write.  An amazing amount of time and effort goes into coding around impendence mismatches:<\/p>\n