How can I use the dependency injection system builtin to ASP.Net 5 to create an instance of the required API controller for me? In your Startup.cs can tell the MVC to register all your controllers as services. services.AddMvc().AddControllersAsServices(); Then you can simply inject the desired controller in your other controller via the DI mechanism and … Read more
The principle purpose of MEF is extensibility; to serve as a ‘plug-in’ framework for when the author of the application and the author of the plug-in (extension) are different and have no particular knowledge of each other beyond a published interface (contract) library. Another problem space MEF addresses that’s different from the usual IoC suspects, … Read more
You might want to take a look at this blog post. It’s using Unity but it should end-up being the same. Basically, use the WebAPI Dependency Resolver. Make sure that everything is mapped properly and it should be fine. If after setting up your DI you still have problem with your OAuth token, let me … Read more
InstancePerHttpRequest and InstancePerApiRequest essentially do the same thing – you get a single instance of your service for each discrete web request. I’ll use InstancePerHttpRequest for the rest of the answer, but keep in mind that these two are interchangeable. InstancePerLifetimeScope means a new instance of the service will be created for every lifetime scope … Read more
You could use Mockito. I am not sure with PostConstruct specifically, but this generally works: // Create a mock of Resource to change its behaviour for testing @Mock private Resource resource; // Testing instance, mocked `resource` should be injected here @InjectMocks @Resource private TestedClass testedClass; @Before public void setUp() throws Exception { // Initialize mocks … Read more
For myself one of the main reasons to use an IoC (and make use of external configuration) is around the two areas of: Testing Production maintenance Testing If you split your testing into 3 scenarios (which is fairly normal in large scale development): Unit testing Integration testing Black box testing What you will want to … Read more
Below is a working example of using DI without anything that involves MVC Controllers. This is what I needed to do to understand the process, so maybe it will help somebody else. The ShoppingCart object gets, via DI, an instance of INotifier (which notifies the customer of their order.) using Microsoft.Extensions.DependencyInjection; using System; namespace DiSample … Read more
Yay! Now it’s testable; I can feed in test doubles (mocks) to the DoIt method. But at what cost? I’ve now had to define 3 new interfaces just to make this testable. And what, exactly, am I testing? I’m testing that my DoIt function properly interacts with its dependencies. It doesn’t test that the zip … Read more
I haven’t worked with OWIN, but when hosting in IIS integrated mode the HttpContext is not populated until after the HttpApplication.Start event is complete. In terms of DI, this means that you cannot rely on using properties of HttpContext in any constructor. This makes sense if you think about it because the application should be … Read more
As documented in the Guice Wiki, you need to install two PrivateModules, each of which exposes a Service with the right annotation for you. public class MyModule extends AbstractModule { @Override protected void configure() { install(new PrivateModule() { @Override public void configure() { // Bind Source to SourceDatabase. bind(Source.class).to(SourceDatabase.class); // Bind @Named(“database”) Service to Service. … Read more