NuGet.Common by: Microsoft

Common utilities and interfaces for all NuGet libraries.

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

NuGet's core types and interfaces for PackageReference-based restore, such as lock files, assets file and internal restore models.

NuGet.Protocol by: Microsoft

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

NuGet.Versioning by: Microsoft

NuGet's implementation of Semantic Versioning.

NuGetDefense by: Curtis Carter

vulnerabilities.

NUglify by: Ron Logan, Alexandre Mutel, Andrew Bullock

NUglify provides minification and compression methods for CSS, JavaScript and HTML files for .NET

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

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 4, is an upgrade from the groundbreaking NUnit 3 framework. 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. Supported platforms: - .NET Framework 4.6.2+ - .NET 6.0+ - .NET 8.0+

NUnit.Analyzers by: NUnit

This package includes analyzers and code fixes for test projects using NUnit 3+. The analyzers will mark wrong usages when writing tests, and the code fixes can be used to used to correct these usages. They will also aid in the transition from NUnit 3 to NUnit 4. Version 3.0 and upwards works in Visual Studio 2019 (version 16.3) or newer and also enables supression of compiler errors such as errors arising from nullable reference types. For Visual Studio 2017 one must use versions below 3.0 - note that these versions are no longer updated, so version 2.10.0 is the last version that works in Visual Studio 2017.

NUnit.Runners by: Charlie Poole

NUnit features a fluent assert syntax, parameterized, generic and theory tests and is user-extensible. A number of runners, both from the NUnit project and by third parties, are able to execute NUnit tests. Version 2.6 is the seventh major release of this well-known and well-tested programming tool. This package includes the NUnit console, gui and pnunit runners and is compatible with all NUnit framework versions 2.0 through 2.6. The NUnit project editor is also included.

NUnit3TestAdapter by: Charlie Poole, Terje Sandstrom

The NUnit3 TestAdapter for Visual Studio, all versions from 2012 and onwards, and DotNet (incl. .Net core), versions .net framework 4.6.2 or higher, .net core 3.1, .net 5 or higher. Note that this package ONLY contains the adapter, not the NUnit framework. For VS 2017 and forward, you should add this package to every test project in your solution. (Earlier versions only require a single adapter package per solution.)

NUnitTestAdapter by: Charlie Poole, Terje Sandstrom

The NUnit TestAdapter for Visual Studio 2012 and newer for NUnit 2. With this package you don't need to install the VSIX adapter package, and you don't need to upload the adapter to your TFS server. Note that this package ONLY contains the adapter, not the NUnit framework.

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.

OctoPack by: Octopus Deploy

Octopus Deploy is an automated deployment tool powered by NuGet. This tool adds a post-build activity to your Visual Studio project, so that an Octopus-compatible NuGet package is produced in the Bin directory whenever a Release build completes.

OpenTelemetry by: OpenTelemetry Authors

OpenTelemetry .NET SDK