NuGet.DependencyResolver.Core by: Microsoft

NuGet client library.

NuGet.Frameworks by: Microsoft

The understanding of target frameworks for NuGet.Packaging.

NuGet.LibraryModel by: Microsoft

NuGet client library.

NuGet.Packaging by: Microsoft

NuGet's implementation for reading nupkg package and nuspec package specification files.

NuGet.Packaging.Core by: Microsoft

The core data structures for NuGet.Packaging.

NuGet.Packaging.Core.Types by: NuGet.Packaging.Core.Types

NuGet v3 core library.

NuGet.ProjectModel by: Microsoft

NuGet client library.

NuGet.Protocol by: Microsoft

NuGet client library.

NuGet.Protocol.Core.Types by: NuGet

NuGet's protocol-level base types used for connecting to API v2 and API v3 repositories.

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.

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.

NuSpec.ReferenceGenerator by: Oren Novotny

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

Ocelot by: Tom Pallister

This 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. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. 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.

OctaPull.RabbitMQ by: emrahtaylan

RabbitMQ yönetimi için generik eklentiler sağlandı