Resolving your own and EPiServer’s dependencies without the EPiServer ServiceLocator
I recently got my hands on a new project at work and wanted to see if I could avoid using EPiServer‘s ServiceLocator to resolve the dependencies in my code. From previous projects I was used to being able to inject whatever I needed directly through the constructor, and felt that I wanted to continue doing so. For instance, my class CanHasCookies implements the interface ICanHasCookies …