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

You're asking several questions here Jarrod, can you be more specific? That is, do you just want to know why your method fails? Or maybe you want a way of using data objects across different projects? I'm assuming you're not trying to use LINQ to SQL as a database mapping layer and that you are using it as a domain model? In which case, do both applications implement the same domain (business processes, validation, etc.)?