Paul Gielens:ThoughtsService

Well, what guidance would be in order? Seems to me that all three topics discuss ways to have a business layer talk to persistent storage. Not directly but through the technology you'll be discussing.

So, do we mix and mangle the various options, choose one path and try to fit every in it? And it's easy to give an answer like 'it depends', but on what then?

With the new features Microsoft is adding to the framework, it's to be expected people get a bit lost by the various options available.

Hi Paul,

I would be very much interested to see how Linq to X stacks up to 'established' technologies. For instance Linq to Entities versus NHibernate.

Rationale being whether developers/architects that need to make decisions for what technology to invest in -today- should choose to go the Microsoft route or stay with the currently available products. And no I absolutely wouldn't mind to see how Linq to Entities stacks up LLBLGEN or what Frans is cooking in terms of integration capabilities :-)

Perhaps (time permitting) you guys could also discuss some of the other Linq technology positioning. Ling to Sql versus datasets, Linq to Xml versus XmLDocument/Xpath, etc.

You might kind of argue that this also falls in the guidance category.

Looking forward to see you guys talk, I'll be there.

- Waseem