.net - Mitigating double mapping model overhead -


After much thought, I have decided to use Link to SQL as a link for my project, but in order to keep business items as I POCO objects

This will give some flexibility because the database schema is outdated and there are some problems that can not be solved because backward compatibility.

I'm thinking of creating something like using the reflection to regenerate or complete the LINQ object in a POCO object.

Question:
Do you know a better way of mapping?

Explanation:
1. I do not want to use NHibernate, entities, etc. 2. I know that reflection is slow

You might want to see something like Jimmy Bougard, who You are saying a lot about him, he has loaded it up and if you want to see it.


Comments