search
Found 58 packages
System.Security.Cryptography.OpenSsl✓
Provides cryptographic algorithm implementations and key management for non-Windows systems with OpenSSL. Commonly Used Types: System.Security.Cryptography.RSAOpenSsl When using NuGet 3.x this package requires at least version 3.4.
v5.0.0
↙ 2.4B / total
System.Security.Cryptography.Csp✓
Provides cryptographic algorithm implementations and key management with Windows Cryptographic API (CryptoAPI). Commonly Used Types: System.Security.Cryptography.RSACryptoServiceProvider System.Security.Cryptography.CspParameters When using NuGet 3.x this package requires at least version 3.4.
v4.3.0
↙ 2.3B / total
System.Security.Cryptography.Cng✓
Provides cryptographic algorithm implementations and key management with Windows Cryptographic Next Generation API (CNG). Commonly Used Types: System.Security.Cryptography.RSACng System.Security.Cryptography.ECDsaCng System.Security.Cryptography.CngKey When using NuGet 3.x this package requires at least version 3.4.
v5.0.0
↙ 4.4B / total
JJ.Framework.Reflection✓
Expressions like "myParam.MyList[i].MyProperty" can be converted to text or their value retrieved or info like { "MyMethod", Parameters = { "myParameter", int, 3 } } Accessor IsIndexer IsNullableType IsProperty IsReferenceType IsStatic IsSimpleType IsDefault GetBaseClasses GetImplementations GetItemType GetPropertyOrException GetUnderlyingNullableTypeFast TypesFromObjects. ReflectionCache with fast GetProperties GetFields GetConstructor GetTypeByShortName. Overloads for PropertInfo.GetValue IsAssignableFrom IsAssignableTo CreateInstance.
v1.5.6877.41324
↙ 144.8K / total
reflectionextensionsexpressionslambdatext
CacheManager.Core✓
CacheManager is an open source caching abstraction layer for .NET written in C#. It supports various cache providers and implements many advanced features. The Core library contains all base interfaces and tools. You should install at least one other CacheManager package to get cache handle implementations.
v3.0.0
↙ 18.3M / total
CachingCacheCacheManagerDistributedRedis
pkg
AddressProviderFramework.Implementations.Ptt
PTT(Turkish Post) implementation for AddressProviderFramework, uses xslx file to populate data. You can get the xlsx file from http://postakodu.ptt.gov.tr/Dosyalar/pk_list.zip
v1.0.3
↙ 5.9K / total
JJ.Framework.Reflection.Legacy✓
For expressions and reflection. Turn lambdas into text: "myParam.MyList[i].MyProperty". Extract structured method call data: { "MyMethod", Parameters = { "myParameter", int, 3 } }. Find types and implementations for plug-ins. Access private members with Accessors. Use ReflectionCache for fast access to properties, fields, methods and indexers. Includes helpers like IsIndexer, IsStatic and more!
v0.250.5203
↙ 3.8K / total
ReflectionExpressionsPlug-InsAccessorReflectionCache
Microsoft.Windows.Compatibility.Shims✓
This package provides infrastructure services and shouldn't be referenced directly from your code. It provides facade assemblies in order to make the Microsoft.Windows.Compatibility package work across all .NET implementations. 6c6b536dffb4da0c45ff14921bfee10265265050 When using NuGet 3.x this package requires at least version 3.4.
v2.0.1
↙ 1.9M / total
Penguin.Reflection
Super helpful Reflection methods for Caching, as well as a static class designed to greatly simplify and speed up reflective searching. Supports (requires, for now) whitelisting assemblies and provides methods such as GetAllImplementations, GetAllTypes, GetDerivedTypes, GetMostDerivedType, GetTypeByFullName and more. Very helpful in MetaData driven systems.
v5.1.0
↙ 171.3K / total
pkg
Eto.Forms
Eto.Forms is a cross platform desktop user interface framework. This framework is built so that you can target multiple platforms with one UI codebase. The goal of this framework is to expose a common API that can be used to build functional applications that run across platforms using their native toolkit. This will make your applications look and work as if it were a native application on all platforms. For advanced scenarios, you can take advantage of each platform's capabilities by wrapping your common UI in a larger application, or even create your own high-level controls with a custom implementations per platform. This framework currently supports creating Desktop applications that work across Windows Forms, WPF, MonoMac, MacOS, and GTK#. In order to run your Eto.Forms based application, you must also install one (or more) of the following packages: - Eto.Platform.Wpf - Eto.Platform.Windows - Eto.Platform.Direct2D - Eto.Platform.Gtk - Eto.Platform.Mac64 - Eto.Platform.MacOS To get more information about how to get started, read the wiki: https://github.com/picoe/Eto/wiki
v2.11.0
↙ 1.2M / total
crossplatformguiuiframework
BitMiracle.Docotic.Pdf.Gdi✓
Provides interoperability between Docotic.Pdf and types from the System.Drawing namespace. Please note that it is not recommended to use this add-on in macOS and Linux environments. The macOS and Linux implementations of the System.Drawing are incomplete and different from the Windows implementation. You might get incorrect and/or inconsistent results if you use the System.Drawing namespace in macOS and Linux environments. It is also not recommended to use this addon within Windows services, ASP.NET Core, and ASP.NET. See the Remarks section here: https://docs.microsoft.com/dotnet/api/system.drawing For documentation, sample code, and API reference, visit https://bitmiracle.com/pdf-library/help Core library NuGet package available at https://www.nuget.org/packages/BitMiracle.Docotic.Pdf/
v9.8.18634
↙ 232.5K / total
PDFsystem.drawinggdigdiplusbitmap
pkg
SharpEqualsTester
Test your C# classes' Equals and GetHashCode implementations with ease
v1.0.0
↙ 9.4K / total
equalsequalitytesttesterhelper
EventFlow✓
# EventFlow   ``` $ dotnet add package EventFlow ``` EventFlow is a basic CQRS+ES framework designed to be easy to use. Have a look at our [getting started guide](https://geteventflow.net/getting-started/), the [do’s and don’ts](https://geteventflow.net/additional/dos-and-donts/) and the [FAQ](https://geteventflow.net/additional/faq/). Alternatively, join our [Discord](https://discord.gg/QfgNPs5WxR) server to engage with the community. Its hopefully getting a reboot to kickstart the upcoming release of v1. ## Features * **Easy to use**: Designed with sensible defaults and implementations that make it easy to create an example application * **Highly configurable and extendable**: EventFlow uses interfaces for every part of its core, making it easy to replace or extend existing features with custom implementation * **No use of threads or background workers** * **MIT licensed** Easy to understand and use license for enterprise ## Versions Development of version 1.0 has started and is mainly braking changes regarding changes related to replacing EventFlow types with that of Microsoft extension abstractions, mainly `IServiceProvider` and `ILogger<>`. The following list key characteristics of each version as well as its related branches (not properly configured yet). * `1.x` Represents the next iteration of EventFlow that aligns EventFlow with the standard packages for .NET. Releases here will only support .NET Standard, .NET Core and .NET versions 6+ going forward. - Released - Still development - Not all projects migrated yet Read the [migration guide](https://geteventflow.net/migrations/v0-to-v1/) to view the full list of breaking changes as well as recommendations on how to migrate. ### Documentation Version 1.x documentation has been pulled into this repository in order to have the code and documentation closer together and have the documentation updated in the same pull-requests as any code changes. The compiled version of the documentation is available at https://geteventflow.net/. ### NuGet package status - 🟢 ported - 💚 newly added to 1.0 - 🟠 not yet ported to 1.0 - 💀 for packages that are removed as part of 1.0 (see the [migration guide](https://geteventflow.net/migrations/v0-to-v1/) for details) Projects - 🟢 `EventFlow` - 🟠 `EventFlow.AspNetCore` - 💀 `EventFlow.Autofac` - 💀 `EventFlow.DependencyInjection` - 🟠 `EventFlow.Elasticsearch` - 🟢 `EventFlow.EntityFramework` - 🟠 `EventFlow.EventStores.EventStore` - 🟢 `EventFlow.Hangfire` - 🟢 `EventFlow.MongoDB` - 🟢 `EventFlow.MsSql` - 💀 `EventFlow.Owin` - 🟢 `EventFlow.PostgreSql` - 🟠 `EventFlow.Redis` - 🟢 `EventFlow.RabbitMQ` - 🟢 `EventFlow.Sql` - 🟢 `EventFlow.SQLite` - 🟢 `EventFlow.TestHelpers` ### Branches - `develop-v1`: Development branch, pull requests should be done here - `release-v1`: Release branch, merge commits are done to this branch from `develop-v1` to create releases. Typically each commit represents a release * `0.x` (legacy) The current stable version of EventFlow and has been the version of EventFlow for almost six years. 0.x versions have .NET Framework support and limited support to the Microsoft extension packages through extra NuGet packages. Feature and bug fix releases will still be done while there's interest in the community. ### Branches - `develop-v0`: Development branch, pull requests should be done here - `release-v0`: Release branch, merge commits are done to this branch from `develop-v0` to create releases. Typically each commit represents a release ### Documentation Version 0.x documentation is (although a bit outdated) is live at https://docs.geteventflow.net/.
pkg
Labradoratory.Fetch
Fetch is a base implementation of the repository pattern that includes a processing pipeline for extending the functionality of a respository. This library also includes entity change tracking to support the pipeline system and base controller implementations to get service implementations off the ground quickly.
v2.0.1
↙ 23.6K / total
repositoryaspnetcore
pkg
Fnv1a128
High-speed FNV-1a 「 128-bit 」 implementations; Using LX4Cnh etc. ✔ Free and Open. MIT License. https://github.com/3F/Fnv1a128 ======================================= gnt /p:ngpackages="Fnv1a128/1.0.0" ================== https://github.com/3F/GetNuTool Fnv1a128 1.0.0.2308+1f4e19a Configuration: RCI Platforms: net40;net472;netcoreapp2.1;net5;netstandard2.0 :: generated by a vsSolutionBuildEvent 1.14.1.34071
v1.0.0
↙ 5.0K / total
algorithmnumbersbignumbersmathmultiplication
pkg
MvcTurbine.GoogleSiteMap
Adds a google sitemap to your application, filled with data from implementations of IGoogleUrlProvider.
v3.0.0
↙ 5.9K / total
pkg
Flame.Build.Lazy
Flame is a collection of modular, open-source .NET libraries that can be leveraged to build a compiler. It provides reusable components and a common compilation pipeline, which can be extended with additional passes, to suit the specific needs of source and target languages. This package (Flame.Build.Lazy) defines lazy implementations for several IR constructs, such as types, fields, methods and properties. If you want to build a compiler with Flame, then I recommend that you also get the Flame.Front package.
v0.10.2
↙ 46.8K / total
Flamecompiler
Microsoft.NETCore.Platforms.Future✓
Provides runtime information required to resolve target framework, platform, and runtime specific implementations of .NETCore packages. This package represents future platforms not yet supported in .NETCore stable release and is subject to change. When using NuGet 3.x this package requires at least version 3.4.
v3.1.0
↙ 20.3K / total
pkg
RestArt.Core
RestArt is the .NET library that allows you to easily send REST API commands and get responses. This is implementations package.
v1.1.0
↙ 3.9K / total
REST
EventFlow.Sql✓
# EventFlow   ``` $ dotnet add package EventFlow ``` EventFlow is a basic CQRS+ES framework designed to be easy to use. Have a look at our [getting started guide](https://geteventflow.net/getting-started/), the [do’s and don’ts](https://geteventflow.net/additional/dos-and-donts/) and the [FAQ](https://geteventflow.net/additional/faq/). Alternatively, join our [Discord](https://discord.gg/QfgNPs5WxR) server to engage with the community. Its hopefully getting a reboot to kickstart the upcoming release of v1. ## Features * **Easy to use**: Designed with sensible defaults and implementations that make it easy to create an example application * **Highly configurable and extendable**: EventFlow uses interfaces for every part of its core, making it easy to replace or extend existing features with custom implementation * **No use of threads or background workers** * **MIT licensed** Easy to understand and use license for enterprise ## Versions Development of version 1.0 has started and is mainly braking changes regarding changes related to replacing EventFlow types with that of Microsoft extension abstractions, mainly `IServiceProvider` and `ILogger<>`. The following list key characteristics of each version as well as its related branches (not properly configured yet). * `1.x` Represents the next iteration of EventFlow that aligns EventFlow with the standard packages for .NET. Releases here will only support .NET Standard, .NET Core and .NET versions 6+ going forward. - Released - Still development - Not all projects migrated yet Read the [migration guide](https://geteventflow.net/migrations/v0-to-v1/) to view the full list of breaking changes as well as recommendations on how to migrate. ### Documentation Version 1.x documentation has been pulled into this repository in order to have the code and documentation closer together and have the documentation updated in the same pull-requests as any code changes. The compiled version of the documentation is available at https://geteventflow.net/. ### NuGet package status - 🟢 ported - 💚 newly added to 1.0 - 🟠 not yet ported to 1.0 - 💀 for packages that are removed as part of 1.0 (see the [migration guide](https://geteventflow.net/migrations/v0-to-v1/) for details) Projects - 🟢 `EventFlow` - 🟠 `EventFlow.AspNetCore` - 💀 `EventFlow.Autofac` - 💀 `EventFlow.DependencyInjection` - 🟠 `EventFlow.Elasticsearch` - 🟢 `EventFlow.EntityFramework` - 🟠 `EventFlow.EventStores.EventStore` - 🟢 `EventFlow.Hangfire` - 🟢 `EventFlow.MongoDB` - 🟢 `EventFlow.MsSql` - 💀 `EventFlow.Owin` - 🟢 `EventFlow.PostgreSql` - 🟠 `EventFlow.Redis` - 🟢 `EventFlow.RabbitMQ` - 🟢 `EventFlow.Sql` - 🟢 `EventFlow.SQLite` - 🟢 `EventFlow.TestHelpers` ### Branches - `develop-v1`: Development branch, pull requests should be done here - `release-v1`: Release branch, merge commits are done to this branch from `develop-v1` to create releases. Typically each commit represents a release * `0.x` (legacy) The current stable version of EventFlow and has been the version of EventFlow for almost six years. 0.x versions have .NET Framework support and limited support to the Microsoft extension packages through extra NuGet packages. Feature and bug fix releases will still be done while there's interest in the community. ### Branches - `develop-v0`: Development branch, pull requests should be done here - `release-v0`: Release branch, merge commits are done to this branch from `develop-v0` to create releases. Typically each commit represents a release ### Documentation Version 0.x documentation is (although a bit outdated) is live at https://docs.geteventflow.net/.
page 1next →