NETStandard.Library by: Microsoft

A set of standard .NET APIs that are prescribed to be used and supported together. 18a36291e48808fa7ef2d00a764ceb1ec95645a5 When using NuGet 3.x this package requires at least version 3.4.

NewId by: Chris Patterson

NewId is an ordered 128-bit unique identifier generator using the Flake algorithm.

Newtonsoft.Json by: James Newton-King

Json.NET is a popular high-performance JSON framework for .NET

Newtonsoft.Json.Bson by: James Newton-King

Json.NET BSON adds support for reading and writing BSON

NLog by: Jarek Kowalski, Kim Christensen, Julian Verdurmen

NLog is a logging platform for .NET with rich log routing and management capabilities. NLog supports traditional logging, structured logging and the combination of both. Supported platforms: - .NET 6, 7, 8, 9 and 10 - .NET Standard 2.0 and 2.1 - .NET Framework 3.5 - 4.8 - Xamarin Android + iOS (.NET Standard) - Mono 4 For integrating NLog with Microsoft.Extensions.Logging, check: https://www.nuget.org/packages/NLog.Extensions.Logging For using NLog with ASP.NET Core, check: https://www.nuget.org/packages/NLog.Web.AspNetCore

NuGet.Configuration by: Microsoft

NuGet's configuration settings implementation.

NuGet.DependencyResolver.Core by: Microsoft

NuGet's PackageReference dependency resolver implementation.

NuGet.Frameworks by: Microsoft

NuGet's understanding of target frameworks.

NuGet.LibraryModel by: Microsoft

NuGet's types and interfaces for understanding dependencies.

NuGet.Packaging by: Microsoft

NuGet's understanding of packages. Reading nuspec, nupkgs and package signing.

NuGet.Protocol by: Microsoft

NuGet's implementation for interacting with feeds. Contains functionality for all feed types.

NuGet.Protocol.Core.v3 by: NuGet

NuGet Protocol for 3.1.0 servers

NuGet.Repositories by: NuGet.Repositories

NuGet v3 core library.

NuGet.RuntimeModel by: NuGet.RuntimeModel

NuGet v3 core library.

NuGet.Versioning by: Microsoft

NuGet's implementation of Semantic Versioning.

NUnit by: Charlie Poole, Rob Prouse, Terje Sandstrom and contributors

NUnit is a unit-testing framework for all .NET languages. It can run on macOS, Linux and Windows operating systems. NUnit can be used for a wide range of testing, from unit testing with TDD to full-fledged system and integration testing. It is a non-opinionated, broad and deep framework with multiple different ways to assert that your code behaves as expected. Many aspects of NUnit can be extended to suit your specific purposes. The latest version, version 5, is an upgrade from the groundbreaking NUnit 3 framework and its major update version 4. It is a modernized version, aimed at taking advantage of the latest .NET features and C# language constructs. If you are upgrading from NUnit 3, be aware of the breaking changes (https://docs.nunit.org/articles/nunit/release-notes/breaking-changes.html#nunit-40). Please see the NUnit 4 Migration Guide (https://docs.nunit.org/articles/nunit/release-notes/Nunit4.0-MigrationGuide.html) and take care to prepare your NUnit 3 code before you do the upgrade. If you're upgrading from NUnit 4, please check the release notes for version 5 (https://docs.nunit.org/articles/nunit/release-notes/framework.html). Supported platforms: - .NET Framework 4.6.2+ - .NET 8.0+ - .NET 10.0+

Ocelot by: Tom Pallister

Ocelot is an API Gateway. The 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. reference tokens. 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.

PCLCrypto by: Andrew Arnott

PCL Crypto provides a consistent, portable set of crypto APIs for .NET 4.5, Windows Store, Xamarin.iOS, Xamarin.Android. This makes it easier to create cross-platform .NET libraries and apps. Crypto functionality includes asymmetric and symmetric encryption and signatures, and key derivation. PCLCrypto calls into each native platform's crypto API for maximum performance. For RSA operations this produces a 2-100X improvement in performance on Android and iOS over using the standard RSACryptoServiceProvider API.

PInvoke.BCrypt by: Andrew Arnott

P/Invoke methods for the Windows BCrypt.dll.

PInvoke.Kernel32 by: Andrew Arnott

P/Invoke methods for the Windows Kernel32.dll.