Repository navigation
Message storage by connection-string name for every RDBMS provider, plus named-connection docs and describe (GH-5127, GH-5156) - #5174
Merged
Conversation
…qlDataSource from the container, and named static tenants
Core: NamedConfigurationDependency.Usage ("message store" vs the default "transport") for the failure text,
an ApplyNamedConnectionString overload taking a full dependency, EnsureNamedConnectionStringsApplied(), and the
named values are applied (thread safe, once) on first access to the message stores too, and at the very top of
the resources discovery. Wolverine.RDBMS: NamedConnectionStringTenants.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…med static tenants No data-source form: the provider takes only connection strings, and Aspire.Microsoft.Data.SqlClient registers SqlConnection, not a data source. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…Source from the container, and named static tenants Aspire.MySqlConnector's AddMySqlDataSource registers MySqlDataSource, which the container overload resolves. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…plus named static tenants SQLite still refuses in-memory databases, now checked when the named value is applied. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…("name")) in the missing-connection remedy
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… never values); aspire.md leads with named connections describe now prints a Named Connection Strings table before anything that needs the values, and reports a MissingNamedConnectionStringsException readably instead of failing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ection form Sections are built from the test-code snippet regions. Pages that already had an "Aspire Integration" section reading the connection string by hand keep it, demoted to "Reading the Connection String Yourself". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
This was referenced Oct 25, 2026
This was referenced Nov 2, 2026
This was referenced Nov 9, 2026
This was referenced Nov 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Message storage registration by connection-string name for every RDBMS provider (GH-5127), plus the docs and
describework for named connections (GH-5156). Second half of the Aspire parity work after #5159 (transports).What's here
PersistMessagesWithPostgresqlUsingNamedConnection(name, ...),NpgsqlDataSourceresolved from the container, named static tenants.SqlConnection, not a data source.MySqlDataSourcefrom the container (what Aspire.MySqlConnector'sAddMySqlDataSourceregisters), named static tenants.NamedConfigurationDependency.Usage("message store" vs the default "transport") for the failure text; anApplyNamedConnectionStringoverload taking a full dependency;EnsureNamedConnectionStringsApplied(). Named values are applied once, thread-safely, on first access to the message stores and at the top of resource discovery. The missing-connection remedy names the Aspire database resource (AddX("server").AddDatabase("name")). Wolverine.RDBMS getsNamedConnectionStringTenants.MissingNamedConnectionStringsExceptionreadably instead of failing.aspire.mdand every transport and durability page lead with the named-connection form. Pages that read the connection string by hand keep that section as "Reading the Connection String Yourself".Naming follows the shipped
...UsingNamedConnectionconvention from #5159 rather than the issue's barePersistMessagesWithX(string name), which would collide with the existing(string connectionString)overloads.All additive; no existing overload changes behaviour. Marten / Polecat / Fisher
IntegrateWithWolverine()paths are untouched.Local gate (CI is off today; the version-bump PR runs full CI for the release)
dotnet build -c Release -f net9.0: PostgresqlTests, SqlServerTests, MySqlTests, OracleTests, SqliteTests, CoreTests, 0 warnings / 0 errors--filter-class "*named_connection*": Postgres 5/5, SQL Server 4/4, MySQL 5/5, Oracle 4/4, SQLite 5/5, CoreTests 12/12Closes #5127
Closes #5156
🤖 Generated with Claude Code
https://claude.ai/code/session_01DCggXgxnG3EBXoR9rrq37U