This client library enables working with the Microsoft Azure Storage services which include the blob and file services for storing binary and text data, and the queue service for storing messages that may be accessed by a client. For this release see notes - https://github.com/Azure/azure-storage-net/blob/master/Common/README.md and https://github.com/Azure/azure-storage-net/blob/master/Common/changelog.txt in addition to the breaking changes https://github.com/Azure/azure-storage-net/blob/master/Common/BreakingChanges.txt Microsoft Azure Storage quickstarts and tutorials - https://docs.microsoft.com/en-us/azure/storage/ Microsoft Azure Storage REST API Reference - https://docs.microsoft.com/en-us/rest/api/storageservices/ This library has been replaced by the following new Azure SDKs. You can read about the new Azure SDKs at https://aka.ms/azsdkvalueprop. The latest libraries to interact with the Azure Storage service are: * https://www.nuget.org/packages/Azure.Storage.Blobs * https://www.nuget.org/packages/Azure.Storage.Queues/ * https://www.nuget.org/packages/Azure.Storage.Files.Shares/ It is recommended that you move to the new package.
This client library enables working with the Microsoft Azure Storage Blob service for storing binary and text data. For this release see notes - https://github.com/Azure/azure-storage-net/blob/master/Blob/README.md and https://github.com/Azure/azure-storage-net/blob/master/Blob/Changelog.txt in addition to the breaking changes https://github.com/Azure/azure-storage-net/blob/master/Blob/BreakingChanges.txt Microsoft Azure Storage quickstarts and tutorials - https://docs.microsoft.com/en-us/azure/storage/ Microsoft Azure Storage REST API Reference - https://docs.microsoft.com/en-us/rest/api/storageservices/ REST API Reference for Blob Service - https://docs.microsoft.com/en-us/rest/api/storageservices/blob-service-rest-api This library has been replaced by the following new Azure SDKs. You can read about the new Azure SDKs at https://aka.ms/azsdkvalueprop. The latest libraries to interact with the Azure Storage service are: * https://www.nuget.org/packages/Azure.Storage.Blobs * https://www.nuget.org/packages/Azure.Storage.Queues/ * https://www.nuget.org/packages/Azure.Storage.Files.Shares/ It is recommended that you move to the new package.
Install Chrome Driver (Win32, macOS, macOS arm64, and Linux64) for Selenium WebDriver into your Unit Test Project. "chromedriver(.exe)" is copied to the bin folder from the package folder when the build process. NuGet package restoring ready, and no need to commit "chromedriver(.exe)" binary into source code control repository. / The MSBuild script that contained this package is free and unencumbered software released into the public domain. / "chromedriver(.exe)" is licensed under the New BSD License.
This package contains binaries needed to use brokers in public client desktop applications. The release notes are available at https://office.visualstudio.com/_git/OneAuth?path=/CHANGELOG.md.
Enables compatiblity with portable libraries targeting previous .NET releases like .NET Framework 4.0 and Silverlight. This package supports retargeting references to classic reference assemblies (mscorlib.dll, system.dll, etc) to new contract assemblies (System.Runtime.dll, System.IO, etc). It does this in a pay-for-play way to prevent consuming assemblies from having to reference all of the contracts that happen to overlap with mscorlib. As such, when using this package you may encounter errors like error CS0012: The type 'WebRequest' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Net.Requests, Version=0.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. To resolve these errors install the package with the same name name as the missing assembly. TFS ID: 1612576, GitHub SHA: https://github.com/dotnet/corefx/tree/f47c814b003d17da52940739e227f04e52b10279 When using NuGet 3.x this package requires at least version 3.4.
StackExchange.Redis.Extensions is a library that extends StackExchange.Redis with higher-level APIs for common application scenarios. Compatible with StackExchange.Redis 2.x and 3.x. Features: - Store and retrieve complex .NET objects with pluggable serialization - Connection pooling with LeastLoaded and RoundRobin strategies - Pub/Sub messaging with typed handlers and error logging - Redis Streams with consumer group support - GeoSpatial indexes (GEOADD, GEOSEARCH, GEODIST) - HyperLogLog for probabilistic cardinality estimation - Distributed locking with IAsyncDisposable auto-release - Bitmap operations for analytics and feature flags - Lua scripting for atomic server-side operations - Hash field expiry (Redis 7.4+ HEXPIRE/HSETEX) - Transparent compression (LZ4, Snappy, Zstd, GZip, Brotli) - Azure Managed Identity support - ASP.NET Core DI integration - Multiple named Redis instances - Tags, Sets, Lists, Sorted Sets, key search Serializer packages (pick one): System.Text.Json, Newtonsoft, MemoryPack, MsgPack, Protobuf, ServiceStack, Utf8Json.
Octopus Deploy is an automated deployment tool powered by NuGet. This tool adds a post-build activity to your Visual Studio project, so that an Octopus-compatible NuGet package is produced in the Bin directory whenever a Release build completes.
This client library enables working with the Microsoft Azure Storage Queue service for storing messages that may be accessed by a client. For this release see notes - https://github.com/Azure/azure-storage-net/blob/master/Queue/README.md and https://github.com/Azure/azure-storage-net/blob/master/Queue/Changelog.txt in addition to the breaking changes https://github.com/Azure/azure-storage-net/blob/master/Queue/BreakingChanges.txt Microsoft Azure Storage quickstarts and tutorials - https://docs.microsoft.com/en-us/azure/storage/ Microsoft Azure Storage REST API Reference - https://docs.microsoft.com/en-us/rest/api/storageservices/ REST API Reference for Queue Service - https://docs.microsoft.com/en-us/rest/api/storageservices/queue-service-rest-api This library has been replaced by the following new Azure SDKs. You can read about the new Azure SDKs at https://aka.ms/azsdkvalueprop. The latest libraries to interact with the Azure Storage service are: * https://www.nuget.org/packages/Azure.Storage.Blobs * https://www.nuget.org/packages/Azure.Storage.Queues/ * https://www.nuget.org/packages/Azure.Storage.Files.Shares/ It is recommended that you move to the new package.
StackExchange.Redis.Extensions is a library that extends StackExchange.Redis with higher-level APIs for common application scenarios. Compatible with StackExchange.Redis 2.x and 3.x. Features: - Store and retrieve complex .NET objects with pluggable serialization - Connection pooling with LeastLoaded and RoundRobin strategies - Pub/Sub messaging with typed handlers and error logging - Redis Streams with consumer group support - GeoSpatial indexes (GEOADD, GEOSEARCH, GEODIST) - HyperLogLog for probabilistic cardinality estimation - Distributed locking with IAsyncDisposable auto-release - Bitmap operations for analytics and feature flags - Lua scripting for atomic server-side operations - Hash field expiry (Redis 7.4+ HEXPIRE/HSETEX) - Transparent compression (LZ4, Snappy, Zstd, GZip, Brotli) - Azure Managed Identity support - ASP.NET Core DI integration - Multiple named Redis instances - Tags, Sets, Lists, Sorted Sets, key search Serializer packages (pick one): System.Text.Json, Newtonsoft, MemoryPack, MsgPack, Protobuf, ServiceStack, Utf8Json.
This client library enables working with the Microsoft Azure Storage File service for storing binary and text data. For this release see notes - https://github.com/Azure/azure-storage-net/blob/master/File/README.md and https://github.com/Azure/azure-storage-net/blob/master/File/Changelog.txt in addition to the breaking changes https://github.com/Azure/azure-storage-net/blob/master/File/BreakingChanges.txt Microsoft Azure Storage quickstarts and tutorials - https://docs.microsoft.com/en-us/azure/storage/ Microsoft Azure Storage REST API Reference - https://docs.microsoft.com/en-us/rest/api/storageservices/ REST API Reference for File Service - https://docs.microsoft.com/en-us/rest/api/storageservices/file-service-rest-api This library has been replaced by the following new Azure SDKs. You can read about the new Azure SDKs at https://aka.ms/azsdkvalueprop. The latest libraries to interact with the Azure Storage service are: * https://www.nuget.org/packages/Azure.Storage.Blobs * https://www.nuget.org/packages/Azure.Storage.Queues/ * https://www.nuget.org/packages/Azure.Storage.Files.Shares/ It is recommended that you move to the new package.
This package provides capability to display in-app updates to your app users when a new version of the application is released.
Install IE Driver(x86) for Selenium WebDriver into your Unit Test Project. "IEDriverServer.exe" is copied to bin folder from package folder when the build process. NuGet package restoring ready, and no need to commit "IEDriverServer.exe" binary into source code control repository. / The MSBuild script that contained this package is free and unencumbered software released into the public domain. / "iedriverserver.exe" is licensed under the Apache license v.2.0.
Conformance POCOs and related functionality for Firely's HL7 FHIR SDK. Is a dependency for the FHIR release-specific NuGet packages, but could be used separately in conformance-only scenario's for release R4 and up.
Install Gecko Driver (Win32, Win64, macOS, macOS arm64, and Linux64) 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.
Octopus Deploy is an automated release management tool for modern developers and DevOps teams. This package contains the ILmerged client library for the HTTP API in Octopus.
Microsoft Concurrency Visualizer for .NET Standard, .NET Core and .NET Framework (Microsoft.ConcurrencyVisualizer.Markers.dll/Microsoft.ConcurrencyVisualizer.Instrumentation SDK Tools). - Document: https://weblogs.asp.net/dixin/port-microsoft-concurrency-visualizer-sdk-to-net-standard-and-nuget - NuGet: https://www.nuget.org/packages/ConcurrencyVisualizer/ - Source: https://github.com/Dixin/ConcurrencyVisualizer Microsoft released the binary only for .NET Framework 4.5, with no NuGet package provided. This NuGet package works for both .NET Core and .NET Framework: - dotnet add package ConcurrencyVisualizer - Install-Package ConcurrencyVisualizer Original Microsoft Visual Studio Concurrency Visualizer doc: https://docs.microsoft.com/en-us/visualstudio/profiling/concurrency-visualizer.
Octopus Deploy is an automated release management tool for modern developers and DevOps teams. This package contains the dotnet tool version of the CLI library for interacting with the HTTP API in Octopus.
XML-RPC.NET - an XML-RPC client library for .Net (see xmlrpcnet-server for the server package). NOTE: this is a pre-release development snapshot of the 3.0.0 release. The recommended stable release is version 2.5.0 which supports both client and server applications.
Octopus is a user-friendly DevOps tool for developers that supports release management, deployment automation, and operations runbooks. This package contains the Octopus CLI (octo), a tool to create and deploy releases, create and push packages, and manage environments with Octopus.
iTextSharp is a port of the iText open source Java library for PDF generation written entirely in C# for the .NET platform. This package contains the last version of the library released under the Mozilla Public License and the LGPL, before the project moved to the AGPL. Use this package if you need a free PDF library for use in closed-source projects.
StackExchange.Redis.Extensions is a library that extends StackExchange.Redis with higher-level APIs for common application scenarios. Compatible with StackExchange.Redis 2.x and 3.x. Features: - Store and retrieve complex .NET objects with pluggable serialization - Connection pooling with LeastLoaded and RoundRobin strategies - Pub/Sub messaging with typed handlers and error logging - Redis Streams with consumer group support - GeoSpatial indexes (GEOADD, GEOSEARCH, GEODIST) - HyperLogLog for probabilistic cardinality estimation - Distributed locking with IAsyncDisposable auto-release - Bitmap operations for analytics and feature flags - Lua scripting for atomic server-side operations - Hash field expiry (Redis 7.4+ HEXPIRE/HSETEX) - Transparent compression (LZ4, Snappy, Zstd, GZip, Brotli) - Azure Managed Identity support - ASP.NET Core DI integration - Multiple named Redis instances - Tags, Sets, Lists, Sorted Sets, key search Serializer packages (pick one): System.Text.Json, Newtonsoft, MemoryPack, MsgPack, Protobuf, ServiceStack, Utf8Json.
StackExchange.Redis.Extensions is a library that extends StackExchange.Redis with higher-level APIs for common application scenarios. Compatible with StackExchange.Redis 2.x and 3.x. Features: - Store and retrieve complex .NET objects with pluggable serialization - Connection pooling with LeastLoaded and RoundRobin strategies - Pub/Sub messaging with typed handlers and error logging - Redis Streams with consumer group support - GeoSpatial indexes (GEOADD, GEOSEARCH, GEODIST) - HyperLogLog for probabilistic cardinality estimation - Distributed locking with IAsyncDisposable auto-release - Bitmap operations for analytics and feature flags - Lua scripting for atomic server-side operations - Hash field expiry (Redis 7.4+ HEXPIRE/HSETEX) - Transparent compression (LZ4, Snappy, Zstd, GZip, Brotli) - Azure Managed Identity support - ASP.NET Core DI integration - Multiple named Redis instances - Tags, Sets, Lists, Sorted Sets, key search Serializer packages (pick one): System.Text.Json, Newtonsoft, MemoryPack, MsgPack, Protobuf, ServiceStack, Utf8Json.
# 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 Gecko Driver(Win64) 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.
This package is an unofficial port of the .NET Framework System.Messaging assembly for .NET Core/.NET 8+ applications running on Windows. It is provided for development convenience. If Microsoft officially releases an MSMQ client package, you should migrate to the official package. The source code for this package is derived from the .NET Framework reference source code.
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. ### 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) ### Commands There are quite a few commands you can call - you should check out the [command reference](https://docs.chocolatey.org/en-us/choco/commands). Here are the most common: - Help - choco --help or choco command --help - Search - choco search something - List - choco list - Config - choco config list - Install - choco install baretail - Pin - choco pin windirstat - Outdated - choco outdated - Upgrade - choco upgrade baretail - Uninstall - choco uninstall baretail #### Alternative installation sources: - Install ruby gem - choco install compass -source ruby - Install python egg - choco install sphynx -source python - Install windows feature - choco install IIS -source windowsfeatures #### More For more advanced commands and switches, use `choco --help` or `choco command --help`. You can also look at the [command reference](https://docs.chocolatey.org/en-us/choco/commands), including how you can force a package to install the x86 version of a package. ### Create Packages? We have some great guidance on how to do that. Where? I'll give you a hint, it rhymes with socks! [Docs!](https://docs.chocolatey.org/en-us/create/create-packages) In that mess there is a link to the [PowerShell Chocolatey module reference](https://docs.chocolatey.org/en-us/create/functions).
StackExchange.Redis.Extensions is a library that extends StackExchange.Redis with higher-level APIs for common application scenarios. Compatible with StackExchange.Redis 2.x and 3.x. Features: - Store and retrieve complex .NET objects with pluggable serialization - Connection pooling with LeastLoaded and RoundRobin strategies - Pub/Sub messaging with typed handlers and error logging - Redis Streams with consumer group support - GeoSpatial indexes (GEOADD, GEOSEARCH, GEODIST) - HyperLogLog for probabilistic cardinality estimation - Distributed locking with IAsyncDisposable auto-release - Bitmap operations for analytics and feature flags - Lua scripting for atomic server-side operations - Hash field expiry (Redis 7.4+ HEXPIRE/HSETEX) - Transparent compression (LZ4, Snappy, Zstd, GZip, Brotli) - Azure Managed Identity support - ASP.NET Core DI integration - Multiple named Redis instances - Tags, Sets, Lists, Sorted Sets, key search Serializer packages (pick one): System.Text.Json, Newtonsoft, MemoryPack, MsgPack, Protobuf, ServiceStack, Utf8Json.
GDAL is a translator library for raster and vector geospatial data formats that is released under an X/MIT style Open Source license by the Open Source Geospatial Foundation. As a library, it presents a single raster abstract data model and single vector abstract data model to the calling application for all supported formats. ** This is a repackage of the third party Gdal project for use with ThinkGeo's Map Suite product line. ** ** You should not need to reference this package directly, it will be a dependency of other Map Suite packages. ** The purpose of the repackage is to enable ThinkGeo to control release and debug versions known to be compatible with various Map Suite products and to provide ongoing backward compatibility independent from the original author. You can find more information at the link below. Why we repackage: http://wiki.thinkgeo.com/wiki/repackagednugetpackages Supported Platforms: Windows, Linux, MacOS, iOS, Android Source Website: https://sourceforge.net/
Install Microsoft Web Driver into your Unit Test Project. "MicrosoftWebDriver.exe" added as a linked project item, and copied to bin folder at the build. NuGet package restoring ready, and no need to commit "MicrosoftWebDriver.exe" binary into source code control repository. / The installing/uninstalling script codes that contained this package are free and unencumbered software released into the public domain.
Install IE Driver(x64) for Selenium WebDriver into your Unit Test Project. "IEDriverServer64.exe" is copied to bin folder from package folder when the build process. NuGet package restoring ready, and no need to commit "IEDriverServer64.exe" binary into source code control repository. / The MSBuild script that contained this package is free and unencumbered software released into the public domain. / "iedriverserver64.exe" is licensed under the Apache license v.2.0.
StackExchange.Redis.Extensions is a library that extends StackExchange.Redis with higher-level APIs for common application scenarios. Compatible with StackExchange.Redis 2.x and 3.x. Features: - Store and retrieve complex .NET objects with pluggable serialization - Connection pooling with LeastLoaded and RoundRobin strategies - Pub/Sub messaging with typed handlers and error logging - Redis Streams with consumer group support - GeoSpatial indexes (GEOADD, GEOSEARCH, GEODIST) - HyperLogLog for probabilistic cardinality estimation - Distributed locking with IAsyncDisposable auto-release - Bitmap operations for analytics and feature flags - Lua scripting for atomic server-side operations - Hash field expiry (Redis 7.4+ HEXPIRE/HSETEX) - Transparent compression (LZ4, Snappy, Zstd, GZip, Brotli) - Azure Managed Identity support - ASP.NET Core DI integration - Multiple named Redis instances - Tags, Sets, Lists, Sorted Sets, key search Serializer packages (pick one): System.Text.Json, Newtonsoft, MemoryPack, MsgPack, Protobuf, ServiceStack, Utf8Json.
# 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/.
Octopus Deploy is an automated release management tool for modern developers and DevOps teams. This package contains the non-ILmerged client library for the HTTP API in Octopus.
Features: - Create named pipe servers that can handle multiple client connections simultaneously. - Send strongly-typed messages between clients and servers: any serializable .NET object can be sent over a pipe and will be automatically serialized/deserialized, including cyclical references and complex object graphs. - Async - Requires .NET Standard 2.0 - Supports large messages - up to 300 MiB. - Server restart automatically - Automatically wait for the release of the pipe for the server, if it is already in use - Automatically waiting for a server pipe creating when client connecting - Automatic reconnect with a given interval and at each `client.WriteAsync`, if necessary - Supports variable formatters, default - BinaryFormatter which uses System.Runtime.Serialization.BinaryFormatter inside - Also available ready formatters in separate nuget packages: H.Formatters.Json - Supports `PipeAccessRule`'s(see `H.Pipes.AccessControl` nuget package) or more complex code to access using the `PipeServer.PipeStreamInitializeAction` property
# 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/.
NUnit features a fluent assert syntax, parameterized, generic and theory tests and is user-extensible. A number of runners, both from the NUnit project and by third parties, are able to execute NUnit tests. Version 2.6 is the seventh major release of this well-known and well-tested programming tool. This package includes the NUnit console, gui and pnunit runners and is compatible with all NUnit framework versions 2.0 through 2.6. The NUnit project editor is also included. This unofficial package is limited to run on the 4.x framework which improves compatibility with Mono when running tests compiled for 4.x.
This package is a counterfeit of the .NET Framework version System.Messaging assembly for .NET Core applications running on Windows Client and Windows Server. It is provided for development convenience. Do not use this package if Microsoft officially releases this package again. Also, once it is released, you should migrate the code to the new package. The source code for this package is excerpted from the .NET Framework reference source code.
Dotnet Repository Update tools
Inno Setup tools packaged for NuGet. This is an unofficial package of the Inno Setup installer, intended for use as a NuGet dependency. This package is kept up to date and with upstream IS releases and includes the following: - 64-bit edition of Inno Setup - support for building both 32-bit and 64-bit installers - Inno Setup Preprocessor - encryption support - official translations of Inno Setup
This client library is the base package for the Azure Storage Data Movement library. The Azure Storage Data Movement library is designed for high-performance, multi-threaded uploading, downloading and copying Azure Storage blobs and files. This library is inteneded to be used with one or more of the Data Movement sub-packages, such as Azure.Storage.DataMovement.Blobs or Azure.Storage.DataMovement.Files.Shares. For this release see notes - https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/storage/Azure.Storage.DataMovement/README.md and https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/storage/Azure.Storage.DataMovement/CHANGELOG.md
This client library enables high-performance, multi-threaded uploading, downloading and copying Azure Storage blobs and containers. The package depends on the Azure.Storage.DataMovement package and can be used in conjuction with other Data Movement sub-packages, such as Azure.Storage.DataMovement.Files.Shares to transfer data between services. For this release see notes - https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/storage/Azure.Storage.DataMovement.Blobs/README.md and https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/storage/Azure.Storage.DataMovement.Blobs/CHANGELOG.md
JetBrains Rider Native Core windows-x86 Release Package Version 233.0.20240606.111404
JetBrains Rider Native Core windows-x64 Release Package Version 233.0.20240606.111404
# 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/.
Dotnet Repository Update tools