Jering.Javascript.NodeJS by: JeremyTCD

This library provides ways to invoke javascript in NodeJS, from .Net applications. On top of providing a way to invoke javascript from .js files on disk, this library provides ways to invoke in-memory javascript in string or Stream form, as well as logic in the NodeJS cache.

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.

Jint by: Sebastien Ros

Javascript interpreter for .NET which provides full ECMA 5.1 compliance.

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.1" /> </ItemGroup> </Project>

JsonSchema.Net.Generation by: Greg Dennis

Extends JsonSchema.Net to provide schema generation functionality

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

Libuv by: Libuv

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

log4net by: The Apache Software Foundation

log4net is a tool to help the programmer output log statements to a variety of output targets. In case of problems with an application, it is helpful to enable logging so that the problem can be located. With log4net it is possible to enable logging at runtime without modifying the application binary. The log4net package is designed so that log statements can remain in shipped code without incurring a high performance cost. It follows that the speed of logging (or rather not logging) is crucial. At the same time, log output can be so voluminous that it quickly becomes overwhelming. One of the distinctive features of log4net is the notion of hierarchical loggers. Using these loggers it is possible to selectively control which log statements are output at arbitrary granularity. log4net is designed with two distinct goals in mind: speed and flexibility

lr.Dotnet.Dotfiles by: Heraeus Digital

Deploys standard dotfiles (.gitignore, .gitattributes, .editorconfig, .aiignore, .dockerignore, .stignore) to consuming projects at build time with smart merge/upsert logic.

lr.Dotnet.SharedMsbuildConfiguration by: Heraeus Digital

Upserts standard nuget.config and Directory.Build.props (with NuGet feed override via env vars) into consuming projects at build time.

lr.Shared.ApiKeyAuthentication by: Tobias Schulz

x

lr.Shared.AzureMonitorTelemetry by: Tobias Schulz

x

lr.Shared.Blazor.DataProtection by: Tobias Schulz

x

lr.Shared.Blazor.FileStorageLogging by: Tobias Schulz

x

lr.Shared.Blazor.Forms by: Tobias Schulz

x

lr.Shared.Blazor.Identity by: Tobias Schulz

x

lr.Shared.Blazor.MicrosoftIdentity by: Tobias Schulz

x

lr.Shared.Blazor.Recharts by: Tobias Schulz

x

lr.Shared.Blazor.SvgGraphs by: Tobias Schulz

x