o_19mgorv9t13a3ko71fev19l81mqa.pdf

I define the mock implementation and bind it to the IProductRepository interface in the AddBindings method
of the NinjectDependencyResolver class in the SportsStore.WebUI project, as illustrated by Listing 7-5.
Listing 7-5. Adding the Mock IProductRepository Implementation 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.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() {
Mock mock = new Mock
mock.Setup(m => m.Products).Returns(new List {
new Product { Name = "Football", Price = 25 },
new Product { Name = "Surf board", Price = 179 },
new Product { Name = "Running shoes", Price = 95 }
});
}
}
}
kernel.Bind().ToConstant(mock.Object);
I had to add a number of namespaces to the file for this addition, but the process I used to create the mock repository
implementation uses the same Moq techniques I introduced in Chapter 6. I want Ninject to return the same mock object whenever
it gets a request for an implementation of the IProductRepository interface, which is why I used the ToConstant
method to set the Ninject scope, like this:
...
kernel.Bind().ToConstant(mock.Object) ;
...
Rather than create a new instance of the implementation object each time, Ninject will always satisfy requests for the
169