This project is read-only.

Future Directions?

Jul 14, 2010 at 5:24 PM
So the victory conditions initially set out for this project was to support the use of the existing SQL database objects, albeit, with a better schema name choice. In addition, since the BCL provider code was open sourced by Microsoft we wanted to supply a set of providers in binary form to ease adoption. Both these objectives were easy to meet. But the question now stands: "Where do we go from here? And do we?" Perhaps it would be interesting to add support for the SQL session state structures and a new ASP.Net session manager. Or since this code base is rather based on hand crafted SQL calls, perhaps we should port it all over to Entity Framework? So I am curious what, if anything, you all would like to see added.