Iced by: iced project and contributors <https://github.com/icedland>

iced is a blazing fast and correct x86 (16/32/64-bit) instruction decoder, disassembler and assembler written in C#. - 👍 Supports all Intel and AMD instructions - 👍 Correct: All instructions are tested and iced has been tested against other disassemblers/assemblers (xed, gas, objdump, masm, dumpbin, nasm, ndisasm) and fuzzed - 👍 100% C# code - 👍 The formatter supports masm, nasm, gas (AT&T), Intel (XED) and there are many options to customize the output - 👍 The decoder decodes >130 MB/s - 👍 Small decoded instructions, only 40 bytes and the decoder doesn't allocate any memory - 👍 Create instructions with code assembler, eg. `asm.mov(eax, edx)` - 👍 The encoder can be used to re-encode decoded instructions at any address - 👍 API to get instruction info, eg. read/written registers, memory and rflags bits; CPUID feature flag, control flow info, etc - 👍 Supports `.NET Standard 2.0/2.1+` and `.NET Framework 4.5+` - 👍 License: MIT

ImageComparison by: Thomas Piart, Jakob XnaFan Krarup

A set of .NET extension methods to get the difference between images and more...

Independentsoft.Office by: Independentsoft

Independentsoft.Office is Office file format API for .NET Framework, .NET Core, .NET Standard, Mono, Xamarin. Supports Word, Excel, PowerPoint, OpenOffice file formats.

Independentsoft.Office.Odf by: Independentsoft

Independentsoft.Office.Odf is Open Document Format API for .NET Framework, .NET Core, .NET Standard, Mono, Xamarin.

Independentsoft.Office.Spreadsheet by: Independentsoft

Independentsoft.Office.Spreadsheet is Excel file format API for .NET Framework, .NET Core, .NET Standard, Mono, Xamarin.

IndexRange by: Bradley Grainger

Implementations of System.Index and System.Range for netstandard2.0 and .NET Framework.

Interop.UIAutomationClient by: Roemer

The UI Automation COM-to-.NET adapter makes it possible to use the new Windows Automation API 3.0 COM interfaces, with their improved reliability and performance, while still using the same System.Windows.Automation classes as in earlier versions of UI Automation

IoC.Container by: NikolayP

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

Irony by: IronyProject

Irony Parser Kit, core library

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.

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-CLR-x86 by: Microsoft

The K Runtime Environment for Desktop CLR x86

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.