IoC.Container by: NikolayP

Simple, powerful and fast expressions based Inversion of Control container for .NET.

IronSnappy by: Ivan Gavryliuk (@aloneguid)

This is a native .NET port of Google Snappy compression/decompression library. The only implementation that is stable, fast, up to date with latest Snappy improvements, and most importantly does not depend on native Snappy binaries. Works everywhere .NET Core runs.

Irony by: Roman Ivantsov

Package Description

Irony.NetCore by: daxnet

Irony.NetCore is a .NET Core compatible version of the Irony framework initially developed and maintained by Roman Ivantsov. Irony is a development kit for implementing languages on .NET platform. In Irony the target language grammar is coded directly in c# using operator overloading to express grammar constructs. Irony's scanner and parser modules use the grammar encoded as c# class to control the parsing process.

Itage.XmlDiffPatch by: Microsoft

A library that compares XML files.

JetBrains.Annotations by: JetBrains

JetBrains.Annotations help reduce false positive warnings, explicitly declare purity and nullability in your code, deal with implicit usages of members, support special semantics of APIs in ASP.NET and XAML frameworks and otherwise increase accuracy of JetBrains Rider and ReSharper code inspections.

JetBrains.dotTrace.CommandLineTools.windows-x64 by: JetBrains

The dotTrace console tool lets you start a profiling session and get performance snapshots from the command line. This can be helpful in various scenarios, like: * profiling an application on a remote server, * automating the process of gathering performance snapshots, for example, as a part of your continuous integration builds, * speeding up profiling routines by creating profiling scripts. The tool supports profiling of .NET Framework, .NET Core, Mono, and Unity applications. The tool is a JetBrains Redistributable Product. This means it is free and can be freely redistributed. Note that it does not require JetBrains dotTrace to be installed on your machine. At the same time, to analyze the collected snapshots, you will need the standalone version of JetBrains dotTrace or JetBrains Rider.

JetBrains.FormatRipper by: Mikhail Pilin, Konstantin Kretov

The cross-platform open-source library for parsing executable and shared-library files. It supports the Compound, ELF, Mach-O, Fat Mach-O, DMG, MSI, and PE formats, providing useful information about their internals.

JetBrains.HabitatDetector by: Mikhail Pilin

The cross-platform open-source library for detecting habitat information.

JetBrains.Profiler.Api by: Mikhail Pilin, Ilia Kirianovskii

JetBrains Profiler API allows you to control profiling sessions right from the code of your application. Use this API in conjunction with JetBrains dotTrace, JetBrains dotMemory, or JetBrains dotCover. This API can also be used in conjunction with JetBrains Self-Profiling API.

JetBrains.Profiler.SelfApi by: Mikhail Pilin, Ilya Ivanov, Kirill Ponimash

JetBrains Self-Profiling API lets you initiate and control profiling sessions right from the code of your application. The snapshots taken by the API calls can be later opened and investigated in JetBrains profiling tools. The main advantage of Self-Profiling API is that it doesn't require the profiling tools to be installed on the end-user machine. For example, you can use this API to take memory snapshots of your application on end-user desktops, staging and production servers, and so on. ATTENTION: Note that for its work JetBrains Self-Profiling API uses the JetBrains.dotMemory.Console and JetBrains.dotTrace.CommandLineTools packages which is distributed under the JetBrains Redistributable Product license: The library is free and can be freely redistributed but disassembling is not allowed.

jnm2.ReferenceAssemblies.net35 by: Microsoft

A community answer to Microsoft’s decision to single out net35 by excluding it from the https://www.nuget.org/packages/Microsoft.NETFramework.ReferenceAssemblies/ package. This package provides the .NET Framework 3.5 reference assemblies so that net35 projects can be built using the dotnet CLI. Example project that targets multiple frameworks: <Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFrameworks>net35;net40;netstandard2.0;netcoreapp3.0</TargetFrameworks> </PropertyGroup> <ItemGroup> <PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies" Version="1.0.0" /> <PackageReference Include="jnm2.ReferenceAssemblies.net35" Version="1.0.0" /> </ItemGroup> </Project>

jQuery by: jQuery Foundation, Inc.

jQuery is a new kind of JavaScript Library. jQuery is a fast and concise JavaScript Library that simplifies HTML document traversing, event handling, animating, and Ajax interactions for rapid web development. jQuery is designed to change the way that you write JavaScript. NOTE: This package is maintained on behalf of the library owners by the NuGet Community Packages project at http://nugetpackages.codeplex.com/

KdTree by: codeandcats@gmail.com, RobIII

Generic multi-dimensional binary search tree.

KRE-CoreCLR-x86 by: Microsoft

The K Runtime Environment for CoreCLR x86

LibLog by: Damian Hickey

A source code package designed primarily for library and framework authors who want dependency free logging support in their component. Also useful in end applications. As of 5.0.0 it works with NetStandard2.0 and SDK projects. For legacy csproj format support use 4.x versions. If you are a library or framework author and you wish to provide logging support in your component there are a number of options: 1) Depend on a specific logging framework 2) Depend on Common.Logging 3) Implement your own ILog interface and make your consumers wire it up. Option 1 is not desirable because it forces your users to use a particular framework. Option 2 is not desirable because it will add yet more nuget package dependencies and project references with associated versioning concerns in addition to wiring up. Option 3 is desirable because it is dependency free but requires that your users to remember to write an adapter and wire things up. This package is a variation of option 3 but will automatically wire things up too. - It will add an ILog, ILogProvider etc to YourRootNamespace.Logging - ILog is one method to implement - Using optimized reflection, it transparently supports NLog, Log4Net, Serilog and Loupe without any wiring up required by an end user, if the end user simply has a reference to any of these logging frameworks.

LibreOfficeLibrary by: Digital Design

Library for operations with documents with LibreOffice

LibTessDotNet by: Remi Gillig

C# port of the famous GLU Tesselator

Libuv by: Libuv

Multi-platform support library with a focus on asynchronous I/O.

LiveCharts.Wpf.NetCore3 by: Beto Rodriguez

Simple, flexible, interactive and powerful data visualization for Wpf (forked from master branch to add Support to netcoreapp3.1)