@dot_NET_Junkie@vborovikov@chucker@mjovanovictech These are all very helpful error messages that make it much easier to find out why your application isn't starting. Error messages in MS.DI are often vague and unhelpful. Countless of developer hours are wasted by the lack of helpful error messages.
@dot_NET_Junkie@vborovikov@chucker@mjovanovictech It will also tell you when there is a registered type with an identical name to the unregistered type you are trying to inject. This is useful, because modern IDEs generate types in a single keystroke by accident.
When it comes to building reusable software libs, trust is a key feature. But this week, the author of #Moq, a popular library for .NET, violated this trust by releasing a version that harvests mail addresses from any machine using Moq. An absolute sin. https://t.co/f0gdKPmEcp
5 .NET libraries for Dependency Injection
Which do you think is the best?
1. AutoFac (in my opinion the best)
2. Ninject
3. Lamar
4. Simple Injector
5. StructureMap
What will you add?
#dotnet#nuget#csharp#dotnetcore
We published Simple Injector v5.4 to NuGet. This release improves support for working with Flowing Scoping as alternative Composition Model to Ambient Scoping. You can find the release notes here: https://t.co/g6Fp5SNW2j
We published Simple Injector v5.3.2 to NuGet. S.I. now shows the full type name (including namespace) in exception messages in case there are other registrations with the same short type name. This makes it easier to distinguish between registrations: https://t.co/pfXJsumOeu
Users that installed core library version v5.2.0 are advised to upgrade to v5.2.1. v5.2.0 contains a concurrency bug that will impact most users running in a multi-threaded environment. See: https://t.co/07hRJL0rTo
We just released Simple Injector v5.2 that aims to fix the nasty binding redirect issues that users were experiencing. Release notes:
https://t.co/PPWcSqLD4I
Blog post:
https://t.co/PpfK4inQmI
Dear Simple Injector user. I pushed an alpha of 5.2 to NuGet that solves this problem concerning DisposeAsync: https://t.co/BdiPiHdiIU. This issue introduces a breaking change, which makes it important for me to get your feedback before RTM. See the issue for more details.