o_19mgorv9t13a3ko71fev19l81mqa.pdf

public object GetService(Type serviceType) {
return kernel.TryGet(serviceType);
}
public IEnumerable GetServices(Type serviceType) {
return kernel.GetAll(serviceType);
}
private void AddBindings() {
kernel.Bind().To
().InRequestScope();
kernel.Bind()
.To
().WithConstructorArgument("discountParam", 50M);
kernel.Bind().To()
.WhenInjectedInto();
}
}
}
The InRequestScope extension method, which is in the Ninject.Web.Common namespace, tells Ninject that it
should only create one instance of the LinqValueCalculator class for each HTTP request that ASP.NET receives.
Each request will get its own separate object, but multiple dependencies resolved within the same request will be resolved using a
single instance of the class. You can see the effect of this change by starting the application and looking at the Visual Studio
Output window, which will show that Ninject has created only one instance of the LinqValueCalculator class. If you
reload the browser window without restarting the application, you will see Ninject create a second object. Ninject provides a range
of different object scopes and I have summarized the most useful in Table 6-3.
Table 6-3. Ninject Scope Methods
Name
InTransientScope()
InSingletonScope()
ToConstant(object)
InThreadScope()
InRequestScope()
Effect
This is the same as not specifying a scope and creates a new object for each dependency that is resolved.
Creates a single instance which is shared throughout the application. Ninject will create the instance if you use
InSingletonScope or you can provide it with the ToConstant method.
Creates a single instance which is used to resolve dependencies for objects requested by a single thread.
Creates a single instance which is used to resolve dependencies for objects requested by a single HTTP request.
Unit Testing with Visual Studio
In this book, I use the built-in unit test support that comes with Visual Studio, but there are other .NET unit-test packages
available. The most popular is probably NUnit, but all of the test packages do much the same thing. The reason I have selected the
Visual Studio test tools is that I like the integration with the rest of the IDE.
To demonstrate the Visual Studio unit-test support, I added a new implementation of the IDiscountHelper interface to
the example project. Create a new file in the Models folder called MinimumDiscountHelper.cs and ensure that the
contents match those shown in Listing 6-26.
Listing 6-26. The Contents of the MinumumDiscountHelper.cs File
using System;
namespace EssentialTools.Models {
public class MinimumDiscountHelper : IDiscountHelper {
144