DLINQ Gotcha: How to fix the DataContext.SubmitChanges() causing an "ObjectDisposedException"
If you are receiving this error, when trying to persist your data with a call to SubmitChanges() on your datacontext, you will find that not only can you not trap it, it blows up your running instance of your webserver… dandy!
It took a lot research to find out what was happening, but eventually Kashif on the ASP.NET forums had the answer: add enlist=false to your connection string. Apparently DLINQ is/is not listening for some kind async event and goes kablooey when it fires. None-the-less, here is an example config string so you can see what I mean. (btw… how on Earth did I ever fix a problem I didn’t make before the internet?)
<add name="DataConnection" connectionString="Data Source=MyServer;Initial Catalog=MyDb;Persist Security Info=True;User ID=wwright;Password=notachance;enlist=false" providerName="System.Data.SqlClient" />