the ‘bee log

Late to the party here, but this video helped me understand how LINQ and ADO.NET for Entities might be used to cover the traditional object-relational mapping bases (and then some). Very cool stuff.

I’m thinking LINQ replaces kludgey Query Object implementations.

We have a comprehensive and nice “Metadata Service” that we’ve invested a fair amount of time in. We use it to drive UI and dynamic SQL. I see us possibly using this service to code-generate the object-to-relational mapping files required by ADO.NET for Entities (our metadata service would be the system of authority for metadata).

I do have some concerns about ADO.NET in an agile codebase… One of the benefits of going with NHibernate over ADO.NET for Entities is that the release cycle might be a bit tighter. Though, will someone write a LINQ implementation for NHibernate? 

Conversely, ADO.NET is professionally supported, though you could always fork NHibernate if you absolutely had to, but is that the business you’re in?

Software architecture is full of hard decisions, no news there. It’s all going to depend on Microsoft hitting the 80/20 rule with this toolkit. 

Looks promising so far!