Hello,
I have added a second LinqToSql dbml to a project within my ASP.Net solution and when I did this I got context errors in all my pages. I discovered that I needed to assign a unque text value to both the Context Namespace and Entity Namespace for each of the dbml's. This fixed the context errors but I also ran across Linq to SQL DataContext Lifetime Management (http://www.west-wind.com/
Thanks!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
OK, so one thing I do is when a page loads I fill a dropdown with all our Customer Names for example. Then later within a grid on the same page the user may change the spelling of one of the Customer Names. Both the dropdown and the grid were filled by the same datacontext; is this an example of a potential problem?
Hi jherington;
To your question:
"I fill a dropdown with all our Customer Names for example. Then later within a grid on the same page the user may change the spelling of one of the Customer Names. Both the dropdown and the grid were filled by the same datacontext; is this an example of a potential problem?"
No, not in that case. When using the same data context, that data context does object tracking of all the tables created in that context and therefore all bound controls see all the changes made at the same time.
Fernando
Ok, thanks so much Fernando,
I actually meant to say that they come from different datacontexts. So basically the combo is filled by contextA with customer names and users will select from the dropdown to filter the grid. The grid is filled by contextB. Both contextA and contextB will pull from the customer table and both return CustomerName. The user will then edit a grid data item and change the spelling of a customer name. Will this throw an exception or will I simply need to rebind the dropdown to show the changes.
Sorry again for not asking the question correctly the first time, but your answer was helpful anyway.
Hi jherington;
In your last post seeming that the changes are made in the data grid control only and not as well in the combo box it will not cause a problem. It will get out of sync, names in the data grid with the ones in the combo box. To prevent that issue clear the items in the combo box and re-execute the query that fills it.
The problem comes in when, lets say you have two controls that allows you to modify the data in it which connect to the same table and lets also say that the first record in the database is modified by the first control, no problem yet, then the same record is modified in the second control which will throw a Change Conflict Exception Row Not Found or Changed. So you will need to set up code to catch and correct the error, known as conflict resolution.
Is there a reason why you are not using the same data context?
Fernando
Business Accounts
Answer for Membership
by: FernandoSotoPosted on 2009-07-21 at 13:35:22ID: 24909054
Hi jherington;
What you did is fine as long as the two DataContext do not reference and change the same table data.
For example lets say you have two data context, DC1 and DC2, and both of them have database A table B with Row 1 loaded from executed Linq queries. If you make a change to the values in row 1 from DC1, DC2 will not know of that change until it tries to make changes to it itself and you will receive a concurrency error on DC2. It is legal to have two data context you just need to be aware of what can go wrong.
Fernando