Microsoft.Extensions.Configuration.EnvironmentVariables 2.1.0-rc1-final

Microsoft.AspNetCore

Microsoft.AspNetCore

Microsoft.AspNetCore

Microsoft.AspNetCore

Microsoft.AspNetCore.All

Microsoft.AspNetCore.All

Microsoft.AspNetCore.All

ASP.NET Core hosting infrastructure and startup logic for web applications.

ASP.NET Core hosting infrastructure and startup logic for web applications. This package was built from the source code at https://github.com/aspnet/Hosting/tree/0724e6cde1149ee1a19bfec9c13a2c9327b71213

Hosting and startup infrastructures for applications.

Hosting and startup infrastructures for applications.

Hosting and startup infrastructures for applications.

Hosting and startup infrastructures for applications.

Hosting and startup infrastructures for applications. When using NuGet 3.x this package requires at least version 3.4.

Logger implementation to support Azure App Services 'Diagnostics logs' and 'Log stream' features. This package was built from the source code at https://github.com/dotnet/aspnetcore/tree/39e0501ee91dcf2b9b885d647795184815fb0408

Logger implementation to support Azure App Services 'Diagnostics logs' and 'Log stream' features. This package was built from the source code at https://github.com/dotnet/aspnetcore/tree/50b7e9c661453874aa7a54a3985d5120564bb2e5

Implementation for higher level API for confidential client applications (ASP.NET Core and SDK/.NET).

Implementation for higher level API for confidential client applications (ASP.NET Core and SDK/.NET).

This project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.