.net .net framework 4.0 ado.net android appengine applescript astoria beos bi c c# c++ clojure cloud clr cocoa touch concurrency couchdb cql curl data services database django dlr dynamic ef entity framework erlang exchange server full-text functional gnome go google gpu groovy haiku hpc html indexes io iphone ironpython ironruby java javascript jquery jruby jvm linq lisp lucene mac math mirah mongodb monitoring natural language nlp node.js object oriented objective-c operating systems oracle orm parallel performance podcasts powershell prototype python rails refactoring remoting reporting services ruby scripting security simpledb solr sql 2008 sql server ssrs systems programming testing tools vala vb virtualization vs 2010 web services webdav windows xml

POCO Entities in ADO.NET 4.0 (Thursday, July 30, 2009) - One of the most anticipated features of the Entity Framework 4.0 is the ability to have POCO (Plain Old CLR Object) entities. This allows developers to produce domain objects free of any persistence baggage, with no requirements imposed inheritance-wise. Up till now entity objects were required to either inherit EntityObject or had to implement IEntityWithKey, IEntityWithChangeTracker

Using Entity Framework with Oracle (Tuesday, December 22, 2009) - I've long thought that the Entity Framework hasn't gotten a fair shake. Sure, there's some room for improvement but for an out-of-the-box ORM that ships with the framework it's not too bad. One thing has always troubled me, though. I was never sure what kind of traction it had with data sources other than SQL Server. Recently in a project circumstances conspired