Scott Hanselman

Hanselminutes Podcast 79 - LINQ to XML

September 04, 2007 Comment on this post [2] Posted in Learning .NET | LINQ | Podcast | Programming | XML
Sponsored By

My seventy-ninth podcast is up. I've been poking around with LINQ to XML and I reports my findings to Carl about life with XDocuments and XElements. We also talk about the bridge classes that link (no pun intended) System.Xml and System.Xml.Linq.

If you have trouble downloading, or your download is slow, do try the torrent with Āµtorrent or another BitTorrent Downloader.

Links from the Show

Do also remember the complete archives are always up and they have PDF Transcripts, a little known feature that show up a few weeks after each show.

Telerik is our sponsor for this show.

Check out their UI Suite of controls for ASP.NET. It's very hardcore stuff. One of the things I appreciate about Telerik is their commitment to completeness. For example, they have a page about their Right-to-Left support while some vendors have zero support, or don't bother testing. They also are committed to XHTML compliance and publish their roadmap. It's nice when your controls vendor is very transparent.

As I've said before this show comes to you with the audio expertise and stewardship of Carl Franklin. The name comes from Travis Illig, but the goal of the show is simple. Avoid wasting the listener's time. (and make the commute less boring)

Enjoy. Who knows what'll happen in the next show?

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Hosting By
Hosted in an Azure App Service
September 07, 2007 6:28
Scott, as always a great show. One comment as a clarification, you mentioned in the show regarding extension methods that you could add a Surname property to an existing class using extension methods. To do that, you would need Extension Members not methods. Currently the extension method implementation requires stateless static/shared methods. Well, if your static class contains a static dictionary which was indexed by the passed in object's GetHashCode... Yuck, that's getting so ugly and unscalable, I'm not even going to keep fleshing this out. As I was stating, the static methods should be stateless method calls not stateful properties.

It is worth mentioning that, while extension methods are powerful, they can indeed be quite dangerous as I mentioned at
September 07, 2007 8:14
You're absolutely right, I mixed members and methods. Thanks for the reminder!

Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.