@moozzyk
I am using DbContext, although there are some cases (like when I require MergeOptions), where I used ObjectContext. But it is used in the dll that contains reference to EntityFramework, and this dll is referenced by main app.
Generally speaking, all my views (except the main view) do not have DataContext assigned at design time (ViewModel-First approach), DataContext are resolved at runtime using DataTemplates, so I am thinking what would cause to such a chain reaction that would make a call to IObjectContextAdapter.
I will try to implement EF6 again and try to completely get rid of ObjectContext, and see if that the exception will remain. If what you are saying is true, then there should be no problem while compiling.
I am using DbContext, although there are some cases (like when I require MergeOptions), where I used ObjectContext. But it is used in the dll that contains reference to EntityFramework, and this dll is referenced by main app.
Generally speaking, all my views (except the main view) do not have DataContext assigned at design time (ViewModel-First approach), DataContext are resolved at runtime using DataTemplates, so I am thinking what would cause to such a chain reaction that would make a call to IObjectContextAdapter.
I will try to implement EF6 again and try to completely get rid of ObjectContext, and see if that the exception will remain. If what you are saying is true, then there should be no problem while compiling.