# 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/.
This package bundles all localized Sample files from the Dynamo bin Release folder.
Emotion is a cross-platform game engine written in C# using .NetCore, with the intent of abstracting the lower levels of game programming, without taking away control from the developer. The core principle is that making games as a programmer should be about coding, and not about drag and drop interfaces, or wrestling with linking libraries and making the same interfaces over and over again. I made this to provide indie developers (and mostly myself) with a foundation which can be extended and adapted to a game's needs. This package is a debug build. For a release version clone and build yourself.
JetBrains Rider Native Core windows-arm64 Release Package Version 233.0.20240606.111404
Rasterizer allows software developers to convert PDF files to image file formats on the fly. Quick and easy conversions from PDF files to JPEG, PNG, TIFF (including multipage), GIF, BMP. DynamicPDF Rasterizer is backed by a great team of developers and support staff. Flexible licensing (including royalty free) is available to meet all your needs. Release Notes: * Corrected runtime identifier folder names in the NuGet package.
# 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/.
A NuGet package for automatically versioning builds via the Git repository they are sitting in. Usage: Tag your releases with "v#.#". Additional Details: https://github.com/Zoltu/Zoltu.Versioning/blob/master/README.md
Reliable unique ID generation and management for distributed applications. Auto-increment IDs reveal sensitive information. UUIDs (also known as GUIDs) are inefficient as primary keys in a database. Having two different IDs is cumbersome and counterintuitive. We can do better. - For a 93-bit UUID replacement that is efficient as a primary key, use the DistributedId. - For a 128-bit 128-bit UUID replacement with the advantages of the DistributedId and practically no rate limits or collisions, at the cost of more space, use the DistributedId128. - To expose IDs externally in a sensitive environment where zero metadata must be leaked, transform them with PublicIdentities. https://github.com/TheArchitectDev/Architect.Identities Release notes: 2.2.0: - Frameworks: Added net9.0 and net10.0. Removed netcoreapp3.1, net5.0, net6.0, net7.0. - Platforms: (.net8.0+) Now available on 32-bit and big-endian platforms also. 2.1.1: - Enhancement: Upgraded package versions. 2.1.0: - Semi-breaking: IPublicIdentityConverter now features additional methods, although the type is generally not user-implemented. - Semi-breaking: HexadecimalIdEncoder's char-based parameters have been renamed from "bytes" to "chars". - Added DistributedId128, a 128-bit (Guid/UInt128) DistributedId variant with practically no rate limits or collisions that also doubles as a version-7 UUID. - Added encoding methods for UInt128. - Added extension methods to transcode between UInt128 and Guid. - Added public identity conversions for UInt128 and Guid. - DistributedIdGeneratorScope and DistributedId128GeneratorScope now expose the CurrentGenerator property, which helps when implementing generators that need to piggyback on the encapsulated generator. 2.0.0: - BREAKING: Removed Fluid. Ambient scopes with startup configuration are now considered undesirable. - BREAKING: Removed ApplicationInstanceId. Ambient scopes with startup configuration are now considered undesirable. - BREAKING: Removed ambient access to IPublicIdentityConverter. Ambient scopes with startup configuration are now considered undesirable. - BREAKING: IdEncoder has been reworked into BinaryIdEncoder, AphanumericIdEncoder, and HexadecimalIdEncoder. - BREAKING: ID decoding methods now throw if the input is too long. This is specially relevant for strings (such as query parameters) where 0123456789123456 and 0123456789123456aaaa should not produce the same ID. - BREAKING: IPublicIdentityConverter now throws on big-endian architectures, instead of risking silent portability issues between architectures. - BREAKING: Now using AmbientContexts 2.0.0. - Semi-breaking: DistributedIds are now always 28 digits, to avoid a change from 27 to 28 digits in the future. Newly generated IDs will be significantly greater than before. Avoid downgrading after upgrading. - DistributedIds can now burst-generate ~128,000 IDs at once before the ~128 IDs per millisecond throttling kicks in. This makes throttling much less likely to be encountered. - DistributedId now stays incremental even under clock adjustments of up to 1 second. (Note that the UTC clock remains unaffected by DST.) - Hexadecimal ID encodings are now supported. - IPublicIdentityConverter now comes with a TestPublicIdentityConverter implementation for unit tests. - Added UnsupportedOSPlatform("browser") to PublicIdentities, due to continuing lack of AES support. 1.0.2: - Now using AmbientContexts 1.1.1, which fixes extremely rare bugs and improves performance. 1.0.1: - Now using AmbientContexts 1.1.0, for a performance improvement.
Scryber.Core is the open-source PDF rendering engine behind Paperwork.Core. It turns HTML templates with CSS styles and SVG drawing, bound to your data, into PDF documents - with flowing pages, data binding, and referenced images, stylesheets and fonts - on .NET and in Blazor WASM. Paperwork.Core is its successor and the recommended package for new projects. It adds a fluent builder, dependency injection and code configuration on top of this same engine, and your templates carry straight across. Scryber.Core still works as it always has, and will continue to be maintained and supported. It is released under the LGPL licence, so you can use it in commercial applications.
With AppDynamics for Windows Azure, users can now: - Monitor the health of their Windows Azure solution - Troubleshoot performance problems in real time - Rapidly diagnose root cause of performance problems - Dynamically scale up and scale down their Windows Azure application based on performance metrics Installing this package will instrument the roles in your Visual Studio solution for monitoring by AppDynamics. There is no traditional Windows wizard-style installation procedure required to use AppDynamics for Windows Azure.
NetSparkleUpdater/NetSparkle is a C# .NET software update framework that allows you to easily download installer files and update your C# .NET Framework or .NET Core software. Built-in UIs are available for WinForms, WPF, and Avalonia; if you want a built-in UI, please reference a NetSparkleUpdater.UI package. You provide, somewhere on the internet, an XML appcast with software version information along with release notes in Markdown or HTML format. The NetSparkle framework then checks for an update in the background, displays the release notes to the user, and lets users download or skip the software update. The framework can also perform silent downloads so that you can present all of the UI yourself or set up your own silent software update system, as allowed by your software architecture. It was inspired by the Sparkle (https://sparkle-project.org/) project for Cocoa developers and the WinSparkle (https://winsparkle.org/) project (a Win32 port).
ICU - International Components for Unicode This package contains the libraries of a full build of ICU4C for Windows (32- and 64-bit). The major version number of the nuget package corresponds to the ICU release. For Linux it is recommended to install the official ICU package that comes with the system.
Octopus Deploy is an automated release management tool for modern developers and DevOps teams. This package contains the .NET CLI library for interacting with the HTTP API in Octopus.
[Superseded] This package became metadata only package for bootstrap "Selenium.WebDriver.GeckoDriver" x-plat NuGet package. Please consider to install "Selenium.WebDriver.GeckoDriver" NuGet package directly instead of this. ---- Install Gecko Driver(Win32) for Selenium WebDriver into your Unit Test Project. "geckodriver.exe" is copied to bin folder from package folder when the build process. NuGet package restoring ready, and no need to commit "geckodriver.exe" binary into source code control repository. / The MSBuild script that contained this package is free and unencumbered software released into the public domain. / "geckodriver.exe" is licensed under the Mozilla Public License Version 2.0.
Import library for Linq.js (linqjs.codeplex.com) for projects compiled with Saltarelle.Compiler. Unfortunately the official version is slightly incompatible with the Saltarelle runtime so you have to use the JS files included in this package instead of the official linq.js release.
ICU - International Components for Unicode This package contains a minimal build (32- and 64-bit) of ICU4C for Windows as described in https://github.com/sillsdev/icu-dotnet/wiki/Minimal-Builds-of-Icu4C. The major version number of the nuget package corresponds to the ICU release. For Linux it is recommended to install the official ICU package that comes with the system.
# 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/.
Install Selenium.WebDriver.PhantomJS into your Unit Test Project. "phantomjs.exe" is copied to bin folder from package folder when the build process. / The MSBuild script that contained this package is free and unencumbered software released into the public domain. / "phantomjs.exe" is licensed under the New BSD License.
A generic cache mechanism that provides config switching between memory, ASP.NET web, AppFabric, memcached and redis cache mechasnisms. Supports advanced features such as cache dependencies and also fully supports AppFabric and redis within Azure. This package contains example code, configuration updates and release notes in addition to the binaries. If you have already installed this package previously, or only require an updated binary, then please update or install the Glav.CacheAdapter.Core package.
This package provides backward-compatible versions of Windows UI features including UWP XAML controls, dense control styles, and Fluent styles and materials. It is part of the Windows UI Library. The WinUI 3 APIs in this package are subject to change in future releases of Project Reunion. This version is intended for preview and not for use in shipping applications.
The file archive app for Seq writes incoming events to a rolling file set for long-term archival storage. Requires Seq 5.1+, for earlier Seq versions use the 2.x series of releases of this package.
This is the 64-bit MonoMac platform for Eto.Forms UI Framework. Eto.Platform.Mac64 uses a modified version of the open source MonoMac for 64-bit, which allows you to create macOS application bundles from any platform. This package creates an .app bundle to run your app on macOS, even on Windows or Linux. By default, the .NET Core runtime will be bundled in Release configuration so your app won't require extra dependencies. Use Eto.Platform.macOS if you want to distribute your app to the Mac App Store. You do not need to use any of the classes of this assembly (unless customizing the MonoMac functionality of the platform), and should just use the UI controls from the Eto assembly.
Chocolatey is a package manager for Windows (like apt-get but for Windows). It was designed to be a decentralized framework for quickly installing applications and tools that you need. It is built on the NuGet infrastructure currently using PowerShell as its focus for delivering packages from the distros to your door, err computer. Chocolatey is brought to you by the work and inspiration of the community, the work and thankless nights of the Chocolatey Team (https://github.com/orgs/chocolatey/people), with Rob heading up the direction. You can host your own sources and add them to Chocolatey, you can extend Chocolatey's capabilities, and folks, it's only going to get better. This is the Chocolatey Library (API / DLL) package which allows Chocolatey to be embedded in your application. ### Information - [Chocolatey Website and Community Package Repository](https://community.chocolatey.org) - [Mailing List](http://groups.google.com/group/chocolatey) / [Release Announcements Only Mailing List](https://groups.google.com/group/chocolatey-announce) / [Build Status Mailing List](http://groups.google.com/group/chocolatey-build-status) - [Twitter](https://twitter.com/chocolateynuget) / [Facebook](https://www.facebook.com/ChocolateySoftware) / [GitHub](https://github.com/chocolatey) - [Blog](https://blog.chocolatey.org/) / [Newsletter](https://chocolatey.us8.list-manage1.com/subscribe?u=86a6d80146a0da7f2223712e4&id=73b018498d) - [Documentation](https://docs.chocolatey.org/en-us/) / [Support](https://chocolatey.org/support)
Conholdate.Total for .NET is a complete package to work with a large number of file formats from Microsoft Wordยฎ, Excelยฎ, PowerPointยฎ, Outlookยฎ, Projectยฎ, Visioยฎ, Adobe Acrobatยฎ, Illustratorยฎ, Photoshopยฎ, AutoCADยฎ, OpenOfficeยฎ and many more. Conholdate.Total for .NET allows you to use any API released under Aspose and GroupDocs for .NET in order to create, convert, read, edit, update and print popular document formats. Moreover, you may view, annotate, watermark, assemble, classify, search, redact, parse, merge and compare documents without needing to install the native applications. It helps you in file format manipulation and document automation via simple API. Conholdate.Total for .NET also includes specialized APIs to read and create barcodes, extract text from images using OCR as well as extract human marked data from questioners, surveys, quizzes, MCQ papers and feedback forms.
(This NuGet package is the latest fork of NetSparkle) NetSparkle is a C# .NET update checker that allows you to easily download installer files and update your C# WinForms/WPF software. You provide, somewhere on the internet, an XML appcast with software version information along with release notes in Markdown or HTML format. The NetSparkle library then checks for an update in the background, displays the release notes to the user, and lets users download or skip the software update. The library can also perform silent downloads so that you can present all of the UI yourself or set up your own silent software update system, as allowed by your software architecture. It was inspired by the Sparkle (https://sparkle-project.org/) project for Cocoa developers and the WinSparkle (https://winsparkle.org/) project (a Win32 port).
Configuration providers that work with docker secrets for Microsoft.Extensions.Configuration. The official package is not yet available, this is an unnoficial version that we can use until it is released officially.
# 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/.
Deprecated: use Microsoft.Maui.Controls.Maps (Windows supported since .NET MAUI 10). The .NET MAUI Community Maps Toolkit is a collection of Maps. This package will be removed in a future release. See https://github.com/CommunityToolkit/Maui/issues/3190
About FineUI ExtJS based open source ASP.NET Controls FineUI Mission Create No JavaScript, No CSS, No UpdatePanel, No ViewState and No WebServices web application Support Browsers IE 8.0+, Chrome, Firefox, Opera, Safari License Apache License 2.0 (Apache) Note: ExtJS is released under GPL v3 license (http://www.sencha.com/license). Demo&Download http://fineui.com/demo/ You can download FineUI from CodePlex or install using NuGet. PM> Install-Package FineUI
Swagger UI is written by the wordnik folks and allows one to interact with a REST API that is documented using the Swagger spec (including swagger's code gen tools). This package makes the latest available for the .NET community. This is packaged with a pre-release version of Swagger.Net which emits the Swagger spec for the ASP.NET Web API. NOTE: Currently broken in IE. Use in other browser.
Important! A long-standing request from some of our users has been to provide an official TypeScript NuGet package to improve the ease of acquisition. Starting with TypeScript 1.8 beta, they will be distributing the TypeScript compiler and the MSBuild task as a NuGet package with every release! Links to the respective packages are below: TypeScript compiler - https://www.nuget.org/packages/Microsoft.TypeScript.Compiler TypeScript MSBuild task - https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild
MVVM<BareknuckleStyle> This package includes a partial class for use in your projects, which should be used as a base class for your notification-enabled class-hierarchy. This way you can extend Blue.MVVM with functionality that may be released in future updates, possibly preventing breaking changes that may be occur between releases. Also, future udates may use the partial class as an extension point.
MSBuild Tasks and Targets that set your Assembly Version, Package Version, and Package Release Notes from your KeepAChangelog-compatible Changelogs.
Munq IOC Container - A very fast Dependency Injection container for Web Applications. 3.1.6 - fixed bad web.config.transform file in package 3.1.5 - corrects the bad implementation for disposing of Request Lifetime instances. 3.1.4 - Disposes of RequestLifeTime instance when HttpRequest ends. 3.1.3 - re-add extension methods introduced in 3.0.4 but went missing :( 3.1.2 - fixes an issue with the ConfigurationLoader causing resolved object to not cast to their own type. 3.1.1 - Release Build, Oops :( 3.1.0 - Adds support for Open Generics 3.0.5 - Adds more information to exceptions. 3.0.4 - Adds extension methods to simplify setting the LifetimeManager for a Registration. Register...).AsAlwaysNew(); Register...).AsCached(); Register...).AsContainerSingleton(); Register...).AsRequestSingleton(); Register...).AsSessionSingleton(); Register...).AsThreadSingleton(); 3.0.3 - This minor release changes ResolveAll to include derived types. 3.0.2 -This minor release will resolve an interface to a registered class without having Register the interface. 3.0.1 -This minor release changes IMunqConfig.RegisterIn's parameter from IDependencyRegistrar to IocContainer so the Resolve methods can be called.
Lets you call into WinRT APIs from Desktop and Centennial apps (WPF, WinForms, ...) We are working on updating this package with the latest release. Meanwhile as a workaround please add the following winmds to your project; 1. The contract winmd for your API (can be found on the msdn page documentation for this API) Can be found under: C:\Program Files (x86)\Windows Kits\10\References\10.0.15063.0\<SDKVersion>\<Contract>\<ContractVersion>\<Contract>.winmd 2. .NET glue assemblies for .NET clients (required for .NET projection and async support) Can be found under: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETCore\v4.5\*WindowsRuntime*.dll 3. Faรงade winmd (required to resolve legacy 8.x type dependencies from above assemblies) Can be found under: C:\Program Files (x86)\Windows Kits\10\UnionMetadata\10.0.15063.0\Facade\Windows.winmd
XML-RPC.NET - an XML-RPC server library for .NET (see xmlrpcnet for the client package). NOTE: this is a pre-release development snapshot of the 3.0.0 release. The recommended stable release is version 2.5.0 of the xmlrpcnet package which supports both client and server applications.
Chrome Headless Shell 151_0_7922_47 files to use with DynamicPDF HtmlConverter for .NET. This will be installed when installing the ceTe.DynamicPDF.HtmlConverter.NET package. DynamicPDF HtmlConverter is backed by a great team of developers and support staff. Flexible licensing (including royalty free) is available to meet all your needs. Release Notes: * Chrome Headless Shell Version 151_0_7922_47.
# 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/.
An Aspire integration for hosting Bun apps. DEPRECATED: Use Aspire.Hosting.JavaScript and builder.AddBunApp(...) instead. This package will be removed in a future release.
Validates a NuGet packages, are dlls in Release Mode, do they have the right version and public key?
An app for Seq that raises an event whenever it detects that a raised event type has not been seen previously. Requires Seq 5.1+, for earlier Seq versions use the 2.x series of releases of this package.
This package contains the shell binary for the Windows API Code Pack needed for Windows Forms Development in the 1.1 version, released by Microsoft in 2009. Modifications by Jacob Slusser until 2020. Modified to use .NET Frameworks 4.6.2 - 4.8.1, .NET 8 - 10 and refactoring by Peter William Wagner, (aka PWagner) 2023 - 2026.