Microsoft.AspNetCore.SignalR.MsgPack by: Microsoft

Provides server-side support for the MsgPack protocol in ASP.NET Core SignalR

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/af22effae4069a5dfb9b0735859de48820104f5b

Microsoft.AspNetCore.SignalR.Protocols.NewtonsoftJson by: Microsoft

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

Microsoft.AspNetCore.SignalR.Redis by: Microsoft

Redis for ASP.NET Core SignalR.

Microsoft.AspNetCore.SignalR.StackExchangeRedis by: Microsoft

Provides scale-out support for ASP.NET Core SignalR using a Redis server and the StackExchange.Redis client. This package was built from the source code at https://github.com/aspnet/AspNetCore/tree/33c2d01092d9a1b7a583fe99a50b15686e2b7de9

Microsoft.AspNetCore.SpaProxy by: Microsoft

Helpers for launching the SPA CLI proxy automatically when the application starts in ASP.NET MVC Core. This package was built from the source code at https://github.com/dotnet/aspnetcore/tree/4442a188f9200a57635373dcd640893c0e8dcc78

Microsoft.AspNetCore.SpaServices by: Microsoft

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

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

Microsoft.AspNetCore.WebSockets by: Microsoft

ASP.NET Core web socket middleware for use on top of opaque servers. This package was built from the source code at https://github.com/aspnet/AspNetCore/tree/0f9ad16b096ca2535d77efd2ad27645449421b44

Microsoft.AspNetCore.WebUtilities by: Microsoft

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

Microsoft.Azure.Amqp by: Microsoft

Package for Azure AMQP

Microsoft.Azure.AppConfiguration.AspNetCore by: Microsoft

Microsoft.Azure.AppConfiguration.AspNetCore allows developers to use Microsoft Azure App Configuration service as a configuration source in their applications. This package adds additional features for ASP.NET Core applications to the existing package Microsoft.Extensions.Configuration.AzureAppConfiguration.

Microsoft.Azure.Common by: Microsoft

Provides infrastructure for common error handling, tracing, configuration, and HTTP/REST-based pipeline manipulation. The package also exposes the CloudContext type, which enables centralized discovery of available Microsoft Azure libraries.

Microsoft.Azure.Common.Dependencies by: Microsoft

Provides popular portable components for a common HTTP pipeline and JSON parsing. This package is included as a dependency to other libraries such as the Microsoft Azure Management Libraries and should not be directly added to your project.

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.Functions.Extensions by: Microsoft

Provides extensions to work with Azure Functions features.

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. This library has been replaced by the following new Azure SDKs. You can read about the new Azure SDKs at https://aka.ms/azsdkvalueprop. The latest libraries to interact with the Azure KeyVault service are: * https://www.nuget.org/packages/Azure.Security.KeyVault.Keys * https://www.nuget.org/packages/Azure.Security.KeyVault.Secrets * https://www.nuget.org/packages/Azure.Security.KeyVault.Certificates It is recommended that you move to the new package.