If you don't want to save changes to b, then why assign b. Name = "name2". Use a temporary variable to store "name2".
Later you can assign it to b. Name if you want.
Not use temporary. User maybe save "b" object. Maybe cancel "b" object.
– ebattulga Mar 30 '10 at 10:42.
My understanding is that the purpose of a DataContext is to encapsulate a set of changes to be submitted together. If you want some changes to be separate, create another DataContext instance. DataContexts, I believe, are intended to be lightweight and quick to create and release.In the application I have created that uses LINQ to SQL heavily, I create a separate DataContext for every window.
Do NOT use a shared data context for your whole application. It's not like a database connection. That's why the database connection is a separate object.
For example, say I have a single object that is part of a large graph. That one single object gets updated (and no other part of the graph). Update single object.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.