Home/ Questions/Q 650209
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T22:01:41+00:00

This is a design question, I noticed that by time by LINQ-to-SQL Context gets

  • 0

This is a design question, I noticed that by time by LINQ-to-SQL Context gets crowded with all the tables from the database, so today I wanted to create a new context for the new tables I added recently. The tables makes up a unit of logic by themselves and they are separated from other tables logically, except for 2 tables. I am planning to redundant those tow tables and put them again in the new context.

My question is that is my design valid, what problems I will face which I am not considering now?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can certainly do that, but make sure you don’t share any tables between the two Contexts. What you need to watch out for are situations where you need both DataContext instances. In other words if you are adding or editing in two contexts at the same time you need to remember to save changes in both. If rows are shared between the two contexts you can lose changes.

    Also remember that you don’t need to use the LINQ to SQL designer’s contexts at all. You can always do

    DataContext context = new DataContext();
Table<SomeL2SClass> table = context.GetTable<SomeL2SClass>();
    • 0