Multiple/single instance of Linq to SQL DataContext

Question

I have a project with a number of different classes querying and modifying data in a common set of tables. I\'ve set up a .dbml file which provides us with a DataContext cla

Answer 1

I've always heard that you should use a single instance of the DataContext. I usually create a singleton instance of my DC in my business logic class, and use it for all my linq queries.

I'm sure some of the linq gurus on here might be able to give you exact reasons as to why you should only have on instance of your data context class... I'm not quite certain.