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

The DataContext class is lightweight enough that you can instantiate it over and over. This makes thing simpler when accessing entity objects within a single method. If you need to access the same LINQ objects from different classes and methods while keeping them attached to the DataContext for tracking purposes, it's also okay to keep a single instance.