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.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.

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+

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. Version 3.0 and upwards works in Visual Studio 2019 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.

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.)

NuProj by: Immo Landwerth

NuProj provides an MSBuild-based approach to create NuGet packages (.nupkg). The build projects are called .nuproj files and are regular MSBuild projects. In general, the definition of a NuProj file is very similar to the NuGet .nuspec file – except that it is done via MSBuild. In fact, NuProj generates the .nuspec file and simply calles NuGet to build the package. Thus, for details you can still refer to the official NuGet documentation. There is also a Visual Studio extension which you find under http://bit.ly/NuProjVS.

NuSpec.ReferenceGenerator by: Oren Novotny

Tool to auto-generate BCL package nuspec dependencies for CoreCLR projects

NWebsec by: André N. Klingsheim

NWebsec is an easy to use security library for ASP.NET applications. With a few lines of config it lets you set important security headers, detect potentially dangerous redirects, control cache headers, and remove version headers. See project website for documentation.

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.

NWebsec.Core by: André N. Klingsheim

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

NWebsec.Mvc by: André N. Klingsheim

NWebsec attributes for ASP.NET MVC 5 applications. NWebsec helps you set important security headers, detect potentially dangerous redirects, control cache headers, and remove version headers. See project website for documentation.

NWebsec.Owin by: André N. Klingsheim

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

O2S.Components.PDF4NET by: O2 Solutions

O2S Pdf 4 Net Dll

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.