We all got that email :D

damn .. march 2007 :) . missed that

The submitter probably just found out about it :)

The source is in .net

I wonder where the article is ... I only saw adds.

no source code :(

I have in fact posted it :) , and yes, there is the Expression Trees thingy in the title , but i felt the accent was on LinqToSql vs NH . And I am really liking NH :P.
Can you tell ? ;)

To me , that has almost NOTHING to do with NHibernate.
I mean sure, strongly typed. But you can't compare that LinqToSql to NHibernate .
You can compare the ToSql part with NHibernate and say : it produces better querys(or not) and compare mapping styles and what you can do with them.

There already is a project LinqToNhibernate. Then you will have type safety.

hmm . .indeed it is.... however none of them seems like will make the front page :(

Well, you might be familiar to the XmlWriter api, i'm not - so when looking at your code and his code, the wrapper looks nicer, and easyer to understand to me.

And i'm not really sure how many know the XmlWriter api so well that they would find hard to read and understand the fluent interface one.

Oh , and at the comment above when i kept writing "link" i meant "linq" :D

damn ... we need some code tags :))

Granted is not the fastest or most efficient way, but it does look good and it seems allot more maintainable to me. Maybe if you have a 10MB xml file you should use XmlWriter, otherwise I would go with this fluent interface.

In the blog comments someone said : why not use link ? - I'm pretty sure you can't do this with link :

XmlOutput xo = new XmlOutput()
.XmlDeclaration()
.Node("root").Within()
.Node("numbers").Within();

for (int i = 1; i <= 10; i++)
xo.Node("number").Attribute("value", i.ToString()).InnerText("This is the number: " + i);

Nice copy paste from : Sams Teach Yourself Microsoft SQL Server 2005 Express in 24 Hours .
That's the way to go ;)

I should look on the bright side then huh ? :D :D

Are you trying to move MSDN over to your page ? otherwise what's the point ? ;(

Other than that, there's no actual tests to show the big improvement.
Unless you're in a tight time critical loop - I'm thinking it's not worth it . :)