Comments on: Linq to SQL DataContext.Attach Heartaches

By: vishal kadiwala

vishal kadiwala — Mon, 18 Oct 2010 12:15:20 +0000

hi,

very much thanks for this solution.
It help’s a lot.
Thanks,

By: Sidar Ok

Sidar Ok — Sat, 23 Aug 2008 01:37:25 +0000

Also, on datacontext disposal thing – in this particular example there happens to be one time the two datacontexts are alive, because a disposable object is disposed at the end of a using scope. So at the inner method who is responsible for deletion the mother data context is still alive, and tracking the object to be deleted.

Hence, db context doesnt want to track an object which is already dirty, and already another context is responsible of it. So disabling the object tracking in the readonly context solves the problem.

In some cases the solution might not be that easy, then you may want to put them in seperate data contexts.

By: Sidar Ok

Sidar Ok — Sat, 23 Aug 2008 01:25:30 +0000

I just discovered this post and felt content Let’s go set up a country now

I am really happy to have helped.

I also have implemented a disconnected, multitiered solution with WCF and linq to SQL and prettty much covered most of the cases that one would encounter during this in 2 blog posts:

http://www.sidarok.com/web/blog/content/2008/05/26/linq-to-sql-with-wcf-in-a-multi-tiered-action-part-1.html

http://www.sidarok.com/web/blog/content/2008/06/02/linq-to-sql-with-wcf-in-a-multi-tiered-action-part-2.html

It also includes the source codes. Hope you’ll enjoy!

By: Andrew Carver

Andrew Carver — Wed, 20 Aug 2008 20:10:54 +0000

Fascinating. I did not know that…