- .NET
- .NET Core 1.1
- 3D
- Android
- Angular
- Angular2
- AngularJS
- apps
- Architecture
- array
- ASP .NET
- async
- await
- Azure
- binding
- C#
- changes
- closure
- cocoa
- code
- collection
- components
- composition
- cross-platform
- delegate
- dependency injection
- design
- desktop
- Development
- escaping
- events
- exception
- for
- generalization
- git
- Holographic
- HoloLens
- HTML
- iCloud
- INotifyPropertyChanged
- iOS
- iPhone
- JavaScript
- learn
- learning
- Mac
- macOS
- Mobile
- mocking
- multi-threading
- MVC
- PC
- properties
- quality
- SQL Server
- Surface
- Swift
- target
- technologies
- technology
- testing
- tools
- types
- TypeScript
- unit tests
- Unity
- UWP
- Visual Studio
- WebAPI
- Windows
- Windows 8
- Windows 10
- Windows Phone
- WPF
- xCode
Archives
Top 10
- Want to learn WPF? Get a book
- How to write good code on first attempt
- Don't set NSPopupButton's menu.items!
- Books do make a difference
- Developing HTML UI for SQL Server data with no middle code (or just a few lines)
- XAML element properties and cut-paste refactoring
- macOS milestone
- How to improve your good code further
- Embedding custom Cocoa macOS views with xibs into frameworks
- Generically handling multi-threading exceptions in WPF
- Follow Code {Sections} on WordPress.com
Tag Archives: dependency injection
Why interfaces?
We should almost always extract interfaces from your service classes because: We should use dependency injection to load and compose implementations: to avoid the need of manually constructing chains of dependent objects and/or to be able to release implementation changes … Continue reading
Posted in Development
Tagged dependency injection, interface, polymorphism, unit tests
Leave a comment
Too much dependency injection?
I’m sure you use dependency injection in many of your projects. And usually, it’s a very good thing to do. However, I found out that many people use it somehow blindly: every time they need to extract a new class just … Continue reading