Hexalith.Memories.Aspire 4.0.0

dotnet add package Hexalith.Memories.Aspire --version 4.0.0
                    
NuGet\Install-Package Hexalith.Memories.Aspire -Version 4.0.0
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Hexalith.Memories.Aspire" Version="4.0.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Hexalith.Memories.Aspire" Version="4.0.0" />
                    
Directory.Packages.props
<PackageReference Include="Hexalith.Memories.Aspire" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Hexalith.Memories.Aspire --version 4.0.0
                    
#r "nuget: Hexalith.Memories.Aspire, 4.0.0"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Hexalith.Memories.Aspire@4.0.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Hexalith.Memories.Aspire&version=4.0.0
                    
Install as a Cake Addin
#tool nuget:?package=Hexalith.Memories.Aspire&version=4.0.0
                    
Install as a Cake Tool

Hexalith.Memories.Aspire

The package also exposes AddHexalithMemoriesAccessTelemetry for the fixed lifecycle and independent-clock topology. It is intentionally disabled by default: Story 27.2 supplies portable Dapr boundaries and component templates, while exact Production adapter selection and behavioral certification remain Story 27.3 work.

.NET Aspire hosting extensions for Hexalith.Memories.

A Hexalith domain module that wants to embed the Memories search-index server in its own *.AppHost (for example to make a curated read model searchable) previously had to hand-roll the same wiring: a Redis Stack search/vector container, a FalkorDB graph container, a secret-store component, a conversation/LLM component, the memories project with a DAPR sidecar, and the standard connection-string / topic environment. That boilerplate now lives here.

Usage

using Hexalith.Memories.Aspire;

// stateStore / pubSub / secretStore are the shared DAPR components the Memories server should reuse
// (for example stateStore/pubSub from Hexalith.EventStore.Aspire's AddHexalithEventStore, and an
// OpenBao-backed secretstores.hashicorp.vault component the consumer provisions and scopes itself).
IResourceBuilder<IDaprComponentResource> secretStore = builder.AddDaprComponent(
    "secretstore",
    "secretstores.hashicorp.vault",
    new DaprComponentOptions { LocalPath = secretStoreYamlPath });

HexalithMemoriesSearchIndexServerResources memories = builder.AddHexalithMemoriesSearchIndexServer(
    stateStore,
    pubSub,
    secretStore,
    llmComponentPath: llmYamlPath,
    daprPlacementHostAddress: placementAddress,
    daprSchedulerHostAddress: schedulerAddress);

// Apply consumer-specific routing on the returned server resource.
_ = memories.Server
    .WithEnvironment("EventStoreIntegration__Routing__SourceToTenantMap__my-source", "my-index")
    .WithEnvironment("EventStoreIntegration__Routing__AutoProvisionRoutedTenants", "true");

The helper only adds the Memories topology and returns the resource builders; the consuming AppHost owns its DAPR component YAML files, its secret-store provisioning (this library never creates a secret-store component or depends on any secret-provider SDK), and any source-to-index routing.

AddHexalithMemoriesAccessTelemetry takes the same externally-provisioned secretStore parameter for the access-telemetry lifecycle, clock, and server components — the consumer supplies one secret-store resource, scoped and named to match its own Dapr configuration (for example access-telemetry-secrets in the OpenBao-backed root AppHost topology):

IResourceBuilder<IDaprComponentResource> accessTelemetrySecretStore = builder.AddDaprComponent(
    "access-telemetry-secrets",
    "secretstores.hashicorp.vault",
    new DaprComponentOptions { LocalPath = accessTelemetrySecretsYamlPath });

HexalithMemoriesAccessTelemetryResources accessTelemetry = builder.AddHexalithMemoriesAccessTelemetry(
    memories.Server,
    stateStoreComponentPath: accessTelemetryStateStoreYamlPath,
    accessTelemetrySecretStore,
    configurationStoreComponentPath: accessTelemetryConfigYamlPath);

By default the helper creates a memories-vectors redis/redis-stack container for the Memories search/vector store. Pass redisConnectionString only when the consuming AppHost owns a compatible Redis Stack dependency.

The memories project is referenced cross-repo with IProjectMetadata.SuppressBuild, so the consuming AppHost never compiles it (Aspire runs children with --no-build) and the two repositories' package graphs stay isolated.

Product Compatible and additional computed target framework versions.
.NET net11.0 is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.0.0 400 11/13/2026
3.0.27 191 11/11/2026
3.0.26 202 11/11/2026
3.0.25 199 11/6/2026
3.0.24 60 11/5/2026
3.0.23 210 11/4/2026
3.0.22 70 11/4/2026
3.0.21 66 11/4/2026
3.0.20 59 11/4/2026
3.0.19 67 11/3/2026
3.0.18 574 11/2/2026
3.0.17 244 11/2/2026
3.0.16 77 11/2/2026
3.0.15 330 11/1/2026
3.0.14 101 11/1/2026
3.0.13 149 10/31/2026
3.0.12 80 10/31/2026
3.0.11 70 10/31/2026
3.0.10 335 10/28/2026
3.0.9 70 10/28/2026
Loading failed