Microsoft.EntityFrameworkCore by: Microsoft

Entity Framework Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations. EF Core works with SQL Server, Azure SQL Database, SQLite, Azure Cosmos DB, MySQL, PostgreSQL, and other databases through a provider plugin API. Commonly Used Types: Microsoft.EntityFrameworkCore.DbContext Microsoft.EntityFrameworkCore.DbSet

Microsoft.EntityFrameworkCore.Abstractions by: Microsoft

Provides abstractions and attributes that are used to configure Entity Framework Core

Microsoft.EntityFrameworkCore.Analyzers by: Microsoft

CSharp Analyzers for Entity Framework Core.

Microsoft.DotNet.PlatformAbstractions by: Microsoft

Abstractions for making code that uses file system and environment testable.

Microsoft.Diagnostics.Runtime by: Microsoft

ClrMD is a set of advanced APIs for programmatically inspecting a crash dump of a .NET program much in the same way that the SOS Debugging Extensions (SOS) do. This allows you to write automated crash analysis for your applications as well as automate many common debugger tasks. In addition to reading crash dumps ClrMD also allows supports attaching to live processes.

Microsoft.Diagnostics.Tracing.EventSource.Redist by: Microsoft

This package includes the class Microsoft.Diagnostics.Tracing.EventSource which enables firing ETW events from managed code. This is the "runtime" or "redist" EventSource package and should be referenced directly only by other NuGet packages that need the EventSource functionality. Application developers that need this functionality should instead reference the Microsoft.Diagnostics.Tracing.EventSource NuGet package which provides an enhanced developer experience. This package enables defining a strongly typed specification of an ETW provider that can be called by managed code. The EventSource class is also included in the .NET Framework, .NET Core, and netstandard2.0 in the System.Diagnostics.Tracing namespace. This package contains the latest version of EventSource and is meant to be used as a stop gap for .NET Framework developers until features and fixes are ported to System.Diagnostics.Tracing.EventSource in the .NET Framework. For more details, have a look at http://msdn.microsoft.com/en-us/library/system.diagnostics.tracing.eventsource.aspx. Commonly Used Types: Microsoft.Diagnostics.Tracing.EventSource

Microsoft.DotNet.Cli.Utils by: Microsoft.DotNet.Cli.Utils

Package Description

Microsoft.DotNet.ProjectModel by: Microsoft.DotNet.ProjectModel

Types to model a .NET Project

Microsoft.DiaSymReader.Native by: Microsoft

Native implementation of PDB file reader and writer. Supported Platforms: - Windows x86 - Windows amd64 - Windows arm - Windows arm64

Microsoft.Data.SqlClient by: Microsoft

The current data provider for SQL Server and Azure SQL databases. This has replaced System.Data.SqlClient. These classes provide access to SQL and encapsulate database-specific protocols, including tabular data stream (TDS). Commonly Used Types: Microsoft.Data.SqlClient.SqlConnection Microsoft.Data.SqlClient.SqlException Microsoft.Data.SqlClient.SqlParameter Microsoft.Data.SqlClient.SqlDataReader Microsoft.Data.SqlClient.SqlCommand Microsoft.Data.SqlClient.SqlTransaction Microsoft.Data.SqlClient.SqlParameterCollection Microsoft.Data.SqlClient.SqlClientFactory When using NuGet 3.x this package requires at least version 3.4.

Microsoft.Data.SqlClient.SNI.runtime by: Microsoft

Internal implementation package not meant for direct consumption. Please do not reference directly. When using NuGet 3.x this package requires at least version 3.4.

Microsoft.Data.SqlClient.SNI by: Microsoft

Internal implementation package not meant for direct consumption. Please do not reference directly. When using NuGet 3.x this package requires at least version 3.4.

Microsoft.Diagnostics.NETCore.Client by: Microsoft

.NET Core Diagnostics Client Library

Microsoft.DotNet.InternalAbstractions by: Microsoft.DotNet.InternalAbstractions

Abstractions for making code that uses file system and environment testable.

Microsoft.Data.OData by: Microsoft Corporation

This version of the library supports earlier versions of the Microsoft OData (V1-V3) protocol only and is not under active development. OData V1-V3 has been superseded by OData V4, which is an industry standard published by OASIS and ratified by ISO. OData V4 is supported through the OData V4 compliant core libraries available at: https://www.nuget.org/packages/Microsoft.OData.Core/ with support documentation available at: https://odata.github.io/odata.net. Note that Asp.Net developers can build OData V4 services using the higher-level OData V4 WebAPI libraries available at: https://www.nuget.org/packages/Microsoft.AspNet.OData/ with support documentation available at: https://odata.github.io/WebApi/. Classes to serialize, deserialize and validate OData payloads. Enables construction of OData producers and consumers. Targets .NET 4.0, Silverlight 4.0 or .NET Portable Lib with support for .NET 4.0, SL 5.0, Win Phone 8, Win Phone 8.1, and Win 8. Localized for CHS, CHT, DEU, ESN, FRA, ITA, JPN, KOR and RUS.

Microsoft.Data.Services.Client by: Microsoft Corporation

LINQ-enabled client API for issuing OData queries and consuming OData payloads. Supports OData v3. Targets .NET 4.0, Silverlight 4.0 or .NET Portable Lib with support for .NET 4.5, Win Phone 8, Win Phone 8.1, and Win 8. Localized for CHS, CHT, DEU, ESN, FRA, ITA, JPN, KOR and RUS.

Microsoft.DotNet.ILCompiler by: Microsoft

Provides a native AOT compiler and runtime for .NET

Microsoft.Data.SqlClient.Extensions.Logging by: Microsoft

Microsoft.Data.SqlClient Extensions Logging - ETW EventSource for SqlClient tracing and diagnostics.

Microsoft.Data.SqlClient.Extensions.Abstractions by: Microsoft

Microsoft.Data.SqlClient Extensions Abstractions

Microsoft.Data.SqlClient.Internal.Logging by: Microsoft

Microsoft.Data.SqlClient Internal Logging - ETW EventSource for SqlClient tracing and diagnostics. This package is for internal use by other Microsoft.Data.SqlClient packages only and should not be referenced directly by application code.