If you've every come across the database pages of codeproject.com, you may have seen a post by me about EntityPool. This library was (at least in my opinion) a very satisfactory solution to the burden of typed datasources and embedded SQL. The library used reflection and ADO.Net to generate sql statements at runtime and simplify the persisting and unpersisting of data object into a database like Sql, MySql, Oracle and Xml files.

The library was used in so many projects I was involved in, that there actually was a suggestion by one of my colleagues to port it to .Net 2.0. Many improvements and tools were suggested, but it all came down to one simple answer from my side: "Why?". The fact of the matter is that there are so many object-relational mapping tools in the open source community, that the continuing existence of EntityPool is hardly feasible.

Nevertheless, the project started out as a learning experience, and for my own benifit I updated the latest sources of the library to the 2.0 framework. Maybe there are some people in the world out there that wish use the code, or see the inner workings. Just drop me a note and perhaps EntityPool is not destined to be nothing more than a memory.