Have you ever had a fully normalized database that you needed to use in your application? Did you wind up using several ugly joins in your code either because the database didn't support views or the DBA wasn't around to create the view for you? Are you sure that join is coded optimally? What happens to your app when one of the tables changes slightly? Yup. We know.

Microsoft knows too. That's why the next generation of ADO.Net aims to solve this problem. By introducing concepts such as LINQ and EntitySQL and the Entity Framework, Microsoft aims to make it possible for developers to create client-side schemas that get "mapped" to the server-side schema. Your application would use just the client-side schema and avoid cross-join madness.

To support these constructs, ADO.Net providers have to increase in sophistication. They have to understand various concepts and know how to map between the different frameworks. This session will present these concepts and demonstrate a working MySQL provider. Using the publicly available vNext bits and our provider you can build these next generation applications.