search

a fast, modern browser for the NuGet registry

built Mar 4, 2026 · v0.1.0

about keyboard shortcuts

NuGet is a registered trademark of Microsoft. This site is not affiliated with Microsoft.

Authaz

search

Found 2,214 packages

Npgsql.NetTopologySuite✓

NetTopologySuite plugin for Npgsql, allowing mapping of PostGIS geometry types to NetTopologySuite types.

v10.0.1

↙ 22.9M / total

npgsqlpostgresqlpostgrespostgisspatial

pkg

HashiCorp.Cdktf.Providers.Postgresql✓

Prebuilt postgresql Provider for Terraform CDK (cdktf) (Stability: Stable)

v12.1.0

↙ 596.7K / total

cdkcdktfpostgresqlproviderterraform

AspNetCore.HealthChecks.UI.PostgreSQL.Storage✓

HealthChecks.UI.PostgreSQL.Storage package contains the required classes to use Postgres NpgSql provider in the UI

v9.0.0

↙ 767.8K / total

HealthCheckHealthChecksHealthPostgreSQL

WorkflowCore.Persistence.PostgreSQL

Provides support to persist workflows running on Workflow Core to a PostgreSQL database.

v3.17.0

↙ 588.3K / total

workflow.NETCorestatemachine

pkg

PostgreSql.Binaries.Lite

Minimum set of binaries of the PostgreSQL database. The one in this file contains postgresql-10.7-1-windows-x64.zip without doc, include, pgAdmin 4, StackBuilder and symbols. So, this package can be consumed from the unit tests. Sample commands to setup a database cluster would be: - extract - cd {extractfolder}\pgsql\bin - initdb -D ..\data - pg_ctl -D ..\data -o "-p {port}" start - perform tests - pg_ctl -D ..\data stop By default, this will start a database (postgres) and allow postgres user accessing it locally with any password (auth_method = trust).

v10.7.1

↙ 361.7K / total

postgresqlx64

RT.Comb

Library to create and use COMB (timestamped sequential) GUID variants for Microsoft SQL Server and PostgreSQL. See the GitHub site for more details.

v4.0.3

↙ 10.2M / total

.NETCombGUIDPostgreSQLAzureSql

Npgsql.DependencyInjection✓

Package Description

v10.0.1

↙ 10.6M / total

npgsqlpostgresqlpostgresadoado.net

Devart.Data.PostgreSql.EFCore✓

dotConnect for PostgreSQL is a high-performance ORM enabled data provider for PostgreSQL that builds on ADO.NET technology. The provider works with .NET Frameworks 2.0+, .NET Core 2.0+, .NET 5+. It supports a wide range of PostgreSQL-specific features, such as secure SSL and SSH connections, PostgreSQL notifications, PostgreSQL bulk data loading, GEOMETRY, PostgreSQL ARRAY types, and others.a More information at https://www.devart.com/dotconnect/postgresql/ License dotConnect for PostgreSQL is available in several editions https://www.devart.com/dotconnect/postgresql/ordering.html The NuGet package initiates the retrieval of an activation key from the Devart website. This key is required to activate the product for a free trial. Key Features * Easy Connection: Allows your application to work with PostgreSQL. * ASP.NET Core: Supports ASP.NET Core Identity. * Performance: Uses many PostgreSQL-specific performance features & optimizations to ensure the highest performance. * Monitoring: Allows per-component tracing of database events with a free dbMonitor application. * Security: Supports various encryption ciphers, SSL and SSH connections, etc. * Support and updates: Enjoy dedicated support team for prompt issue resolution and regular updates to keep your software running smoothly and securely.

v9.1.33.10

↙ 594.9K / total

postgresqlpostgrespgEntityFramework

dotConnect.Express.for.PostgreSQL✓

A free Express edition of dotConnect for PostgreSQL, an enhanced database connectivity solution built over ADO.NET architecture and a development framework with a number of innovative technologies.

v8.4.290

↙ 537.6K / total

PostgreSQLpostgresadoADO.NETprovider

SD.LLBLGen.Pro.DQE.PostgreSql✓

LLBLGen Pro is a leading ORM framework and entity modelling solution for .NET. This package contains the Dynamic Query Engine for PostgreSql. This package has an indirect dependency on Npgsql, the ADO.NET provider for PostgreSql, and it has to be present on the system at runtime. For .NET 4.5.2 and up it's not necessary to reference the ADO.NET provider directly in your project. For .NET Standard 2.0 and up, you have to reference the Npgsql package as well. See the LLBLGen Pro Runtime Framework documentation for details.

v5.13.0

↙ 612.7K / total

LLBLGenProDQEDynamicQuery

ThinkGeo.PostgreSql

ThinkGeo.PostgreSql targets .NET Framework 4.6.2+ and .NET Standard 2.1, compatible with modern .NET runtimes. It is a layer extension to the ThinkGeo product line that provides the ability to render Postgres Spatial data on a map. PostgreSQL, often simply Postgres, is an object-relational database, with additional "object" features – with an emphasis on extensibility and standards compliance. As a database server, its primary function is to store data securely, and to allow for retrieval at the request of other software applications. It can handle workloads ranging from small single-machine applications to large Internet-facing applications (or for data warehousing) with many concurrent users; on macOS Server, PostgreSQL is the default database; and it is also available for Microsoft Windows and Linux (supplied in most distributions). ** This is an extension for use in ThinkGeo's product line, and cannot be used standalone. ** Docs and Product Guides: https://docs.thinkgeo.com/ This is a commercial product with a free 30-day evaluation. Start your evaluation by signing up at https://helpdesk.thinkgeo.com/register and downloading the ProductCenter application. Supported Platforms: Windows, Linux Other ThinkGeo Products based on .NET: ThinkGeo.UI.Maui ThinkGeo.UI.Android ThinkGeo.UI.iOS ThinkGeo.UI.Blazor ThinkGeo.UI.Wpf ThinkGeo.UI.WinForms ThinkGeo.GisServer

v14.4.5

↙ 439.3K / total

SpatialGISThinkGeo.NETCorePostgreSql

EventFlow.PostgreSql✓

# EventFlow ![EventFlow logo](https://raw.githubusercontent.com/eventflow/EventFlow/develop-v1/icon-128.png) ![NuGet downloads](https://img.shields.io/nuget/dt/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/.