3 ms·
How does it remove anything beneficial? I look at DI, or really the dependency inversion pattern, as a guard that encourages better/more maintainable code. Can
by briHass 11y ago
How does it remove anything beneficial?
I look at DI, or really the dependency inversion pattern, as a guard that encourages better/more maintainable code. Can you write good code without it, sure, and you can write bad code with it, but it's much more likely that code written with it is easier to trace and maintain. Not to mention much easier to test.
The configuration based, hot-swapping of dependencies...that I've never seen much need for even in larger projects.
- deleted 11y ago[deleted]
- briHass 11y agoSince this is a C# thread, there are a number of ways to navigate through the interface to the implementation in Visual Studio: 1. Right-click, Go To Implementation (Ctrl-F12) 2. Right-click, Find All References (shows the interface and impl) 3. (Resharper) Navigate, Dervived Symbols (Alt-End) Even the new method info in Visual Studio 2015 (2013 Enterprise) is able count and show you the usages as a tip through the interface. I don't experience any issues with this pattern; the tooling is built around it.
- rjbwork 11y ago4. There's a plugin for ReSharper called Agent Mulder that examines your AutoFac configuration and knows when something is registered and can take you right to it.