WPF Linq to SQL applications. Some best practices controlling contracting and Master/Detail views

Well we feel I'm blank something here since I'm carrying problems and cant
find any solutions to this rudimentary scenario.Application
Technology:WPF, 3.5(sp1) framework, LINQ to SQL, o/r engineer CRUD, Visual
studio 2008, C#.Apllication Layout:Main plans contains a Panel on a left
holding ListBoxes that are generated organization to linq-to-sql entities
(to a perspective of a ToList() slight of a entites), Buttons underneath a
list grant we to supplement / mislay / edit. The Buttons also enclose a
calm filter for a items. If we select to correct or add, a new window
opens adult beside a uncanny Panel and it's a Master/Detail perspective
form. The equipment in this form are organization by XAML with a
CollectionViewSource.My experiences:When adding elements to a
Master/Detail form, there is too many over with a DataContext that was
automobile generated my a O/R designer, with calls to InsertOnSubmit() and
DeleteOnSubmit(), and lastly SubmitChnages().The reason for 1 as good is
that we try to use ObservableCollections wherever we can to hang a linq
entities ToList() IList, since differently we am not means to filter a law
simply in memory and bond a items. If a BindingListCollectionView doing by
linq-to-SQL entites certified filtering, that would graceful many make my
day.When we emanate a new Master/Detail view, we pass a uncanny
ObservableCollection and emanate a new perspective for it (mainly since we
use XAML to bond a form, and to cut down on code). When a new vigilant is
total to a uncanny list, a Panel Window doesn't arrangement a item, though
a list doesn't get re-sorted and a indexes get screwed up.When we try to
use Entities that are family in my database and are tangible as EntitySets
in a O/R engineer generated crud, we am forced to use a returned
BindingListCollectionView that is not filterable (see #2). The wholly
proceed we found around this is indeed to query a family myself and force
them into an QbservableCollections as well. This increases loading time
and is unwieldy given all a entities now need specific
ObservableCollection wrappers and not a general one.When controlling named
styles, there are quirks we only can't figure out. For instance:<Setter
Property="CheckBox.Foreground" Value="#333333" /><Setter
Property="TextBlock.Foreground" Value="#333333" />The above impression set
on a tip turn contained in a page would set all a TextBlocks to a
repremand foregound color, though would have no outcome on CheckBoxes.
CheckBoxes would need to have a specific style="" ability set to that
impression and wholly afterwards would that work.So distant I'm removing a
feeling that presumably I'm doing some things horribly wrong or many of
these technologies aren't unequivocally as mature as we initial guess they
would be during this stage. Is anyone means to assistance with any of
these issues or only yield a Best Practice for what we wish to grasp
(defined in a concentration plans partial during a top)? we humbly ask
your help.Thanks, Eric.<p />