Microsoft.AspNetCore.Server.HttpSys by: Microsoft

ASP.NET Core HTTP server that uses the Windows HTTP Server API. This package was built from the source code at https://github.com/aspnet/AspNetCore/tree/e7f262e33108e92fc8805b925cc04b07d254118b

Microsoft.AspNetCore.Server.IIS by: Microsoft

Provides support for hosting ASP.NET Core in IIS using the AspNetCoreModule. This package was built from the source at: https://github.com/aspnet/IISIntegration/tree/0b5973e5014f17e7bbdbe57c28b90d2b9b1d2347

Microsoft.AspNetCore.Server.IISIntegration by: Microsoft

ASP.NET Core components for working with the IIS AspNetCoreModule.

Microsoft.AspNetCore.Server.Kestrel by: Microsoft

ASP.NET Core Kestrel cross-platform web server.

Microsoft.AspNetCore.Server.Kestrel.Https by: Microsoft

HTTPS support for the ASP.NET Core Kestrel cross-platform web server.

Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv by: Microsoft

Libuv transport for the ASP.NET Core Kestrel cross-platform web server.

Microsoft.AspNetCore.Session by: Microsoft

ASP.NET Core session state middleware.

Microsoft.AspNetCore.SignalR.Common by: Microsoft

Common serialization primitives for SignalR Clients Servers This package was built from the source code at https://github.com/dotnet/dotnet/tree/c22dcd0c7a78d095a94d20e59ec0271b9924c82c

Microsoft.AspNetCore.SignalR.Protocols.Json by: Microsoft

Implements the SignalR Hub Protocol using System.Text.Json. This package was built from the source code at https://github.com/dotnet/aspnetcore/tree/f6b3a5da75eb405046889a5447ec9b14cc29d285

Microsoft.AspNetCore.SignalR.Redis by: Microsoft

Redis for ASP.NET Core SignalR.

Microsoft.AspNetCore.SpaServices by: Microsoft

Helpers for building single-page applications on ASP.NET MVC Core.

Microsoft.AspNetCore.StaticFiles by: Microsoft

ASP.NET Core static files middleware. Includes middleware for serving static files, directory browsing, and default files.

Microsoft.AspNetCore.TestHost by: Microsoft

ASP.NET Core web server for writing and running tests.

Microsoft.AspNetCore.WebSockets by: Microsoft

ASP.NET Core web socket middleware for use on top of opaque servers.

Microsoft.AspNetCore.WebUtilities by: Microsoft

ASP.NET Core utilities, such as for working with forms, multipart messages, and query strings.

Microsoft.Azure.Cosmos by: Microsoft

This client library enables client applications to connect to Azure Cosmos DB via the NoSQL API. Azure Cosmos DB is a globally distributed, multi-model database service. For more information, refer to http://azure.microsoft.com/services/cosmos-db/.

Microsoft.Azure.Cosmos.Direct by: Microsoft

Internal implementation package not meant for direct consumption. Please do not reference directly.

Microsoft.Azure.Cosmos.Table by: Microsoft

This client library enables working with the Microsoft Azure CosmosDB Table storage, with support for global distribution, automatic secondary indexes, dedicated throughput, and single-digit millisecond latency. See "Getting started with the Azure Cosmos DB: Table API" at https://aka.ms/premiumtables. For reporting issue, please file it at: https://github.com/Azure/azure-cosmos-table-dotnet/issues.

Microsoft.Azure.DocumentDB.Core by: Microsoft

This client library enables client applications targeting .NET Core to connect to Azure Cosmos DB via the DocumentDB (SQL) API. Azure Cosmos DB is a globally distributed, multi-model database service. For more information, refer to http://azure.microsoft.com/services/cosmos-db/.

Microsoft.Azure.KeyVault by: Microsoft

Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. Azure Key Vault supports multiple key types and algorithms and enables the use of Hardware Security Modules (HSM) for high value customer keys. In addition, Azure Key Vault allows users to securely store secrets in a Key Vault; secrets are limited size octet objects and Azure Key Vault applies no specific semantics to these objects. A Key Vault may contain a mix of keys and secrets at the same time, and access control for the two types of object is independently controlled. Users, subject to appropriate authorization, may: 1) Manage cryptographic keys using Create, Import, Update, Delete and other operations 2) Manage secrets using Get, Set, Delete and other operations 3) Use cryptographic keys with Sign/Verify, WrapKey/UnwrapKey and Encrypt/Decrypt operations. Operations against Key Vaults are authenticated and authorized using Azure Active Directory. Key Vault now supports certificates, a complex type that makes use of existing key and secret infrastructure for certificate operations. KV certificates also support notification and auto-renewal as well as other management features.