I will often take a few moments during a presentation to get a chuckle by bringing up the SharedConnectionWorkflowCommitWorkBatchService . Due to the sheer length of the type name, it's sure to bring a smile or two in one of my otherwise snore-inducing presentation. The other day, while reviewing a deck for a colleague I brought up that he should mention this type, and that it usually gets a laugh from a developer audience. He then asked, "Is that really the longest type name in the framework?" My response, "Well, I'm not really sure, I bet you could do some LINQ magic in order to figure it out." Well, sitting on the bus this morning with some traffic time to spare (and needing to work on my LINQ skills a bit), put together some code. My goal was to go through all of the types, calculate their length and figure out which one was the longest named type. You can replicate this, create a new console application, right click to add references, and select all the references you want to add into this comparison. I added all of the system.* assemblies, PresentationFramework, PresentationCore and WindowBase. You could do even more by selecting everything in the reference dialog. The thing that appeals to me about LINQ is really that i can just write a query, I don't have to worry about looping through a number of times. I also like the fact I can develop by refining, that is, I can get a collection back, tweak the
Read More...