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

NuGet v3 core library.

NuGet.ProjectModel by: NuGet.ProjectModel

NuGet v3 core 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.

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

Ocelot Api Gateway

OctaPull.RabbitMQ by: emrahtaylan

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

OpenLayers by: OpenLayers Team

Open source javascript based mapping API.

OpenTracing by: The OpenTracing Authors

This library is a .NET implementation of the OpenTracing API. To fully understand this platform API, it's helpful to be familiar with the OpenTracing project and terminology more generally. For the time being, mild backwards-incompatible changes may be made without changing the major version number. As OpenTracing and opentracing-csharp mature, backwards compatibility will become more of a priority.

OpenXmlPowerTools by: Eric White

The Open XML PowerTools provides guidance and example code for programming with Open XML Documents (DOCX, XLSX, and PPTX). It is based on, and extends the functionality of the Open XML SDK. It supports scenarios such as: •Splitting DOCX/PPTX files into multiple files. •Combining multiple DOCX/PPTX files into a single file. •Populating content in template DOCX files with data from XML. •High-fidelity conversion of DOCX to HTML. •Searching and replacing content in DOCX/PPTX using regular expressions. •Managing tracked-revisions, including detecting tracked revisions, and accepting tracked revisions. •Updating Charts in DOCX/PPTX files, including updating cached data, as well as the embedded XLSX. •Retrieving metrics from DOCX files, including the hierarchy of styles used, the languages used, and the fonts used. •Writing XLSX files using far simpler code than directly writing the markup, including a streaming approach that enables writing XLSX files with millions of rows.

OpenXMLSDK-MOT by: Microsoft Open Technologies Inc.

https://github.com/OfficeDev/Open-XML-SDK

pclcrypto by: Andrew Arnott

PCL Crypto provides a consistent, portable set of crypto APIs for .NET 4.5, Windows Phone 8.0 SL & 8.1 Xaml, 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.

PCLCrypto by: Andrew Arnott

PCL Crypto provides a consistent, portable set of crypto APIs for .NET 4.5, Windows Phone 8.0 SL & 8.1 Xaml, 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.

PCSC by: Daniel Mueller

Contains classes to access the Personal Computer/Smart Card Resource Manager using the system's native PC/SC API. Implements partial ISO7816 support (APDU etc.). The library is written to run on both, Windows and Unix (Linux with Mono using PCSC Lite).

PDF.Core by: Iron Software https://IronPdf.com

IronPDF for .Net Core 2.x and 3.x allows developers to create, edit and extract PDF content within .Net Core Applications & Websites. The Iron PDF Core library takes the frustration out of generating PDF documents by not relying on proprietary APIs. "Html-To-Pdf" renders pixel-perfect PDFs from open standard document types: HTML, JS, CSS, JPG, PNG, GIF, and SVG. In short, it uses skills that developers already posses. Key features include: * "Html-To-Pdf" creates PDF files from HTML, CSS, JavaScript, and Images. * "Url-To-Pdf" generates PDFs from existing html pages by simply providing their URL. * "Image-To-PDF" creates PDF documents from image files. * PDF to Image functionality can render PDF documents to image files. * Extract text and images from existing PDFs. * Create, Fill and read data from PDF forms. * Merge, Split and Manipulate PDFs to edit PDF structure and content. * Add Page Numbers, Headers, Footers, Watermarks, Tables, Text and Image Assets. * Edit, Stamp and Watermark PDF files with text, images and HTML * Apply HTML or PDF backgrounds to PDF pages * Sign PDF files with digital certificates IronPDF can be used within ASP.NET projects, MVC, Web Services, Console & Desktop Applications. Requires .Net Core 2.x, 3.x or higher. Supports Windows, Ubuntu, Debian, CentOS, BSD, MacOS and Azure platforms. Licensing & Support available for commercial deployments. For code examples, documentation & more visit http://ironpdf.com For support please email us at developers@ironsoftware.com