LINQ to SQL - mapping exception when using abstract base classes

Question

Problem: I would like to share code between multiple assemblies. This shared code will need to work with LINQ to SQL-mapped classes.

I\'ve encountered the same issu

Answer 1

This looks like a bug - we special case Single on a primary key to do a local lookup but it looks like this code path is not grabbing the metadata properly.

The 1=1 hack will mean it goes via a normal database round-trip but really a bug should be filed...