I had a discussion with a colleague about Linq to SQL. I'm still new to .NET, so he thinks I need to know more. (Nevertheless, 30 years of general programming experience should count in my interests, right?) I read several books, and for the new project I decided to use the ADO.NET Entity Data Model. My colleague did not agree, because he “knew” that the entities had many problems. This caused a memory leak on the database server, and Microsoft will stop it anyway. He told me that I should use the data module. Just add .dbml to my project and use the link on top of this.
He has 5 years experience in .NET, which is 4 years more than my experience.
I stopped, so I would not call him a moron or an idiot or something else, because it seems to me that he believes that "SQL Link" == "Entity Data Model" ...
However, I have a little doubt. I thought Linq to SQL is based on .dbml files, which is based on data models. And I heard that Linq to SQL has several technical problems and will soon be replaced by the Entity model. If my colleague mixed them, then he was a stupid moron. But since he has 5 years of experience, and since I doubt that my employee even hired morons, I have doubts.
So what exactly is "Linq to SQL" exactly?
source
share