o_19mgorv9t13a3ko71fev19l81mqa.pdf

private EFDbContext context = new EFDbContext();
}
}
public IEnumerable Products {
get { return context.Products; }
}
This is the repository class. It implements the IProductRepository interface and uses an instance of
EFDbContext to retrieve data from the database using the Entity Framework. You will see how I work with the Entity
Framework (and how simple it is) as I add features to the repository.
To use the new repository class, I need to edit the Ninject bindings and replace the mock repository with a binding for the real
one. Edit the NinjectDependencyResolver.cs class file in the SportsStore.WebUI project so that the
AddBindings method looks like Listing 7-15.
Listing 7-15. Adding the Real Repository Binding in the NinjectDependencyResolver.cs File
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web.Mvc;
using Moq;
using Ninject;
using SportsStore.Domain.Abstract;
using SportsStore.Domain.Concrete;
using SportsStore.Domain.Entities;
namespace SportsStore.WebUI.Infrastructure {
public class NinjectDependencyResolver : IDependencyResolver {
private IKernel kernel;
public NinjectDependencyResolver(IKernel kernelParam) {
kernel = kernelParam;
AddBindings();
}
public object GetService(Type serviceType) {
return kernel.TryGet(serviceType);
}
public IEnumerable GetServices(Type serviceType) {
return kernel.GetAll(serviceType);
}
}
}
private void AddBindings() {
kernel.Bind().To();
}
The new binding is in bold. It tells Ninject to create instances of the EFProductRepository class to service requests
for the IProductRepository interface. All that remains now is to run the application again. Figure 7-13 shows the
results, which demonstrate the application is getting its product data from the database, rather than the mock repository.
182