Tag Archives: dependency injection

Xamarin and Autofac: How DependencyService and Dependency Injection are working together


via Xamarin and Autofac: How DependencyService and Dependency Injection are working together | Anton Kalcik.

The Xamarin.Forms includes DependencyService to help shared code to resolve platform specific implementation. The important thing here is that DependencyService isn’t replace for Dependency Injection container. DependencyService is rather service locator than IoC container. I will show you how they can work together. Although I’m using Autofac as IoC, the proposed design and architecture should be applicable to any IoC Container.

Dependency injection framework for Swift


via Swinject/Swinject · GitHub.

Swinject is a lightweight dependency injection framework for Swift, inspired by Ninject, Autofac,Typhoon, and highly inspired by Funq.

Dependency injection (DI) is a software design pattern that implements Inversion of Control (IoC) for resolving dependencies. In the pattern, Swinject helps your app split into loosely-coupled components, which can be developed, tested and maintained more easily. Swinject is powered by the Swift generic type system and first class functions to define dependencies of your app simply and fluently.

Dependency Injection in NodeJS


via Dependency Injection in Node.js | RisingStack.

Dependency injection is a software Design Pattern in which one or more dependencies (or services) are injected, or passed by reference, into a dependent object.

Forward references in Angular 2


via Forward references in Angular 2.

In our article on Dependency Injection in Angular 2 we explored what dependency injection actually is, and how it is implemented in the Angular 2 framework. If you haven’t read that article yet, I highly recommend you doing so, since this article is based on it.

In a another article we even learned about host and visibility of dependencies as another aspect of Angular 2’s DI system. But that doesn’t mean that we’ve already discovered all features of the machinery yet. In this article we’ll take a look at forward references. Another tiny, yet useful feature of the DI system in Angular 2.

Showpitch Advanced Part 2: Using Neat Architecture for Logging


Last week we reviewed using Neat Architecture for Showpitch‘s Domain Services. This week we’re going to go in to Neat and Logging on Showpitch. At Showpitch we’ve built on the Logging Interceptor that’s offered in Neat. But it’s a fantastic starting point! Using this we get a lot of functionality right out of the box […]

http://blog.johnbrunnings.com/2015/08/05/showpitch-advanced-part-2-using-neat-architecture-for-logging/

Host and Visibility in Angular 2’s Dependency Injection


via Host and Visibility in Angular 2’s Dependency Injection.

In our article on Dependency Injection in Angular 2 we explored what dependency injection actually is, and how it is implemented in the Angular 2 framework. If you haven’t read that article yet, I highly recommend you doing so, since this article is based on it.

Even though we learned that Angular 2’s new dependency injection is very flexible and solves pretty much all the problems we have with the dependency injection in AngularJS, there are still a couple of topics that we haven’t discussed yet. One of them is how Angular treats the relationship between host and child injectors, and the other one is how the visibility of dependencies are handled. In this article we’re going to explore exactly these two topics.

EJB Dependency injection misunderstandings


When I’m doing interviews, I like to ask the following question (provided that the candidate has real life experience with EJBs): There are two stateless session beans, A and B. A has a dependency on B; at what point can bean A use its injected (@EJB) dependency? This turns out to be a tough question, […]

http://tamasgyorfi.com/2014/11/20/ejb-dependency-injection-misunderstandings/