ADO.NET Data Services Hooking POC V3

The third version of my ADO.NET Data Services Hooking POC is released.


The IUpdatable interface is partially implemented. I am waiting for an answer to my thread to implement ClearChanges and ResetResource methods.


Note that it’s a POC, so my tests are very primitive. If you find a bug, let me know and please send me a code to reproduce it at matthieu.mezil at winwise.fr.


I will use this post to answer some questions:


Why having a class hierarchy like this for my entities?


  • EmployeeBase (abstract)
    • Employee
    • ManagerBase (abstract)
      • Manager
      • TeamManager

With ADO.NET Data Services, you can’t have inheritance between the classes you expose. So if you want to expose some employees and some managers, you can’t have Manager inheriting Employee.


Why defining relationships in the exposed classes and not in the base?


An employee has a Manager property and a Manager has also a Manager property. But if you define the Manager property in EmployeeBase, you have a NullReferenceException when you want to get the metadata. It’s a framework bug which will probably be fixed in next version.

This entry was posted in 7671, 7674, 8975, 9060. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>