Microsoft.AspNetCore.Server.HttpSys by: Microsoft

ASP.NET Core HTTP server that uses the Windows HTTP Server API.

Microsoft.AspNetCore.Server.IISIntegration by: Microsoft

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

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

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

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

Transport abstractions for the ASP.NET Core Kestrel cross-platform web server.

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

Managed socket 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 by: Microsoft

Components for providing real-time bi-directional communication across the Web.

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/89c8f6a112d37d2ea8b77821e56d170a1bccdc5a

Microsoft.AspNetCore.SignalR.Core by: Microsoft

Real-time communication framework for ASP.NET Core.

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/6254f5ca64f85b90327592dff67ea6b2ec0262c6

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. This package was built from the source at: https://github.com/aspnet/javascriptservices/tree/15884cbadb94d880c77111017e76e8d37d8d4a72

Microsoft.AspNetCore.SpaServices.Extensions by: Microsoft

Helpers for building single-page applications on ASP.NET MVC Core. This package was built from the source at: https://github.com/aspnet/javascriptservices/tree/3265b92086cb62a98d7a486f9e8f81a77ef56afc

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. This package was built from the source code at https://github.com/aspnet/AspNetCore/tree/9e73c3382f4d9e6ba47afff6a1467ace945c77e7

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.