Thread by @davidfowl

One of the beauties of shared abstractions is once the ecosystem starts to take advantage of them, adding value becomes that much more impactful. This is one of the goals of Microsoft.Extensions.* that we built while developing ASP.NET Core #dotnetcore #aspnetcore

It serves as a building block for what we call "application models" and attempts to handle the boring boilerplate and cross cutting concerns like dependency injection, logging and configuration.

The strategy is multi pronged:
- Introduce libraries with minimal dependencies that other libraries can take a dependency on without too much burden (ILogger, IConfiguration, IOptions, IHostingEnvironment) etc.

- Bootstrap enough "providers" to have a useful base (ini/Json/xml configuration, serilog logger, log4net logger) so that libraries see value in taking a dependency.

- Providing a hosting layer for wiring up that applications can use to wire up these libraries (Microsoft.Extensions.Hosting)

As a result, when we or any other 3rd party add features to any of these layers, the community benefits for free. Here's an example of adding support for hosting windows services to any generic host based application

I hope to see you all extending Microsoft.Extensions.* nuget.org/packages?q=Mic…