3 ms·
The way Asp.net encourages inscrutable code through spooky action-at-a-distance dependency injection patterns is one of the things I actively dislike about wor
by thrower123 6y ago
The way Asp.net encourages inscrutable code through spooky action-at-a-distance dependency injection patterns is one of the things I actively dislike about working with C#. Fortunately, you can avoid most of it and be more explicit if you want, it's just not the idiomatic way. There's almost always an escape hatch to ditch the overblown abstraction layers and get down to what's actually happening.
If all else fails there's dotPeek and Reflector...
- marsven_422 6y agoAnd thus killing of the ability to do proper unit testing.
- thrower123 6y agoIf that pattern is required for proper unit-testing, I don't want to do 'proper' unit testing. You can write code where your dependencies are injected and can be swapped out for testing without buying into a framework that makes it that difficult to reason about what code is actually being run and in what order.