As you already mentioned EF assembly is there only to satisfy DI/IoC configuration, there are zero dependencies on the actual EF assembly (if you have ReSharper you can right click and find usages on the assembly in the Northwind.Web) which is really the concern your after. However for the teams where the assembly is to much to bear because of this (some of teams as well), you can just have your DI/IoC configuration run for each project when your app starts up and wire the assemblies it needs in each project, the caveat here is all your DI/IoC will be configured at each project/layer vs. all of them in the Web or in your case WPF project, which a lot of teams prefer.
↧