NuGet.Protocol.Core.v3 by: NuGet

NuGet Protocol for 3.1.0 servers

NuGet.Repositories by: NuGet.Repositories

NuGet v3 core library.

NuGet.Resolver by: Microsoft

NuGet's dependency resolver for packages.config based projects.

NuGet.RuntimeModel by: NuGet.RuntimeModel

NuGet v3 core library.

NuGet.Versioning by: Microsoft

NuGet's implementation of Semantic Versioning.

Nullable by: Manuel Römer

A source code only package which allows you to use .NET's new nullable attributes in older target frameworks like .NET Standard 2.0 or the "old" .NET Framework. This package does not contain any compiled binaries, but instead adds the attribute classes as C# source code to your project. Because this code is compiled together with the rest of your code, the built binaries will not have a dependency on this package, meaning that you can perfectly use it for both libraries and applications. The C# code is only included if you are targeting a framework version which does not support the new nullable attributes. For example, if you create a library which multi-targets .NET Standard 2.0 and 2.1, the majority of the attributes are not included in the .NET Standard 2.1 version, because it already provides these by default. Please see https://github.com/manuelroemer/Nullable for additional information on how to use this package.

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+

NUnit.ConsoleRunner by: Charlie Poole Rob Prouse

This package includes the console runner and test engine for version 3 and higher of the NUnit unit-testing framework. Any extensions, if needed, may be installed as separate packages.

NUnit.Extension.Net462PluggableAgent by: Charlie Poole Rob Prouse

This extension allow the NUnit engine to run tests under .NET 4.6.2.

NUnit.Extension.Net80PluggableAgent by: Charlie Poole Rob Prouse

This extension allow the NUnit engine to run tests under .NET 8.0.

NUnit.Extension.Net90PluggableAgent by: Charlie Poole Rob Prouse

This extension allow the NUnit engine to run tests under .NET 9.0.

NWebsec.AspNetCore.Core by: André N. Klingsheim

This library provides shared functionality for the NWebsec ASP.NET Core security libraries.

NWebsec.AspNetCore.Middleware by: André N. Klingsheim

NWebsec middleware for ASP.NET Core applications. NWebsec helps you set important security headers and detect potentially dangerous redirects. See project website for documentation.

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.

Ocelot.Administration by: Tom Pallister

Provides Ocelot extensions to use the administration API and IdentityService dependencies that come with it

OneOf by: Harry McIntyre

F# style discriminated unions for C#, using a custom type OneOf<T0, ... Tn> which holds a single value and has a .Match(...) method on it for exhaustive matching. Simple but powerful.

OPCFoundation.NetStandard.Opc.Ua.Core by: OPC Foundation

OPC UA Core Class Library

OPCFoundation.NetStandard.Opc.Ua.Gds.Server.Common by: OPC Foundation

OPC UA GDS Server Class Library

OPCFoundation.NetStandard.Opc.Ua.Types by: OPC Foundation

OPC UA Type Library

OpenAI by: OpenAI

The official .NET library for the OpenAI service API.