Aspire integration

Ignyte.Inquiry.Aspire registers an Inquiry provider from the connection name that Aspire passes to a project. It also registers Inquiry tracing, metrics, logging, and the inquiry readiness health check.

Install the Aspire integration and add a direct reference to the provider package whose source generator the application uses. The Aspire package carries the runtime adapters for all providers, but excludes their analyzers from transitive flow. Do not directly reference multiple provider packages in the same application because each contains a dialect-specific source generator.

dotnet add package Ignyte.Inquiry.Aspire
dotnet add package Ignyte.Inquiry.PostgreSql

Define the database and pass its connection to the application in the AppHost:

var postgres = builder.AddPostgres("postgres")
    .AddDatabase("orders");

builder.AddProject<Projects.Orders_Api>("orders-api")
    .WithReference(postgres)
    .WaitFor(postgres);

Use the same resource name in the application project:

using Inquiry.DependencyInjection;

var builder = WebApplication.CreateBuilder(args);

builder.AddServiceDefaults();
builder.Services.AddInquiry();
builder.Services.AddInquiryGeneratedStores();
builder.AddInquiryPostgreSql("orders");

AddInquiryPostgreSql reads ConnectionStrings:orders, builds and registers one NpgsqlDataSource, and configures Inquiry to open connections from that shared pool. Aspire supplies the setting for the WithReference(postgres) call. The extension also:

calls AddInquiryTelemetry();
subscribes OpenTelemetry to the Inquiry activity source and meter;
calls AddHealthChecks().AddInquiry().

The same resource-name interface is available for AddInquirySqlServer, AddInquiryMySql, AddInquiryMariaDb, AddInquirySqlite, and AddInquiryOracle.

Existing data sources

All provider registrations can use an existing data source:

NpgsqlDataSource dataSource = /* configured and owned by the application */;
builder.Services.AddInquiryPostgreSql(dataSource);

Inquiry opens pipeline connections from that data source and does not dispose it. The application that creates the data source remains responsible for its lifetime. SQL Server accepts a DbDataSource; SqlClientFactory.CreateDataSource creates the provider's internal implementation. SQLite and Oracle accept the same generic DbDataSource contract.

For an externally configured MySqlDataSource, enable AllowUserVariables when generated GUID keys use Inquiry's emulated RETURNING path.

Table of Contents

Aspire integration

Existing data sources