Simple Injector

The official channel for the Simple Injector Dependency Injection library.

[Simple Injector @simpleinjector]

@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.

[Simple Injector @simpleinjector]

@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.

[Simple Injector @simpleinjector]

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

[Marcin Hassenpflug @hashenik]

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

[David Roth @rothdave]

@jbogard That would literally kill support for non-conforming containers like @simpleinjector

[Simple Injector @simpleinjector]

Do you remember when you joined Twitter? I do! #MyTwitterAnniversary

[Simple Injector @simpleinjector]

We added new documentation that provides guidance for using your DI Container inside your testing suite: https://t.co/vL3ilnv9Xx

[John Hinz @jhinz]

Dependency Injection With Simple Injector in .NET - Code Maze https://t.co/Ibt2hM0Tmb

[Simple Injector @simpleinjector]

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

[Eager Beaver @eagerbeavertech]

https://t.co/YSuOUSVO90
Configure Simple Injector in https://t.co/jNmVSPHYdw Core MVC.

[Simple Injector @simpleinjector]

@Mohamed30882898 Nope

[Simple Injector @simpleinjector]

Four years ago, we reached 1 million downloads on NuGet. Today, there are over 18 million.

[Simple Injector @simpleinjector]

Sweet! Today #SimpleInjector reached the 1M downloads milestone on @NuGet. https://t.co/t1ymxmzHVA

[Simple Injector @simpleinjector]

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

[Simple Injector @simpleinjector]

We released Simple Injector v5.3.1 that fixes a bug concerning calls to GetRegistration and GetService: https://t.co/6ChskFIVid

[Simple Injector @simpleinjector]

16 million Simple Injector downloads on NuGet and still going strong: https://t.co/t1ymxmRjka

[Simple Injector @simpleinjector]

We released Simple Injector v5.3 containing several small features and improvements. For more information, go to: https://t.co/aLvTXaO3i4

[Simple Injector @simpleinjector]

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

[Simple Injector @simpleinjector]

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

[.NET Junkie @dot_NET_Junkie]

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.

[Read the Docs @readthedocs]

We had a brief outage earlier today. We are still working with our hosting provider to get back to full capacity, but things should be mostly back up.