[Submission] InfinityFlow.Aspire.Temporal - .NET Aspire Integration for Temporal

[ElanHasson]

Project link

https://github.com/InfinityFlowApp/aspire-temporal

Language

.NET

Short description (max 256 chars)

Aspire extension to run the Temporal CLI dev server as a container resource, with a client library for automatic connection string resolution, OpenTelemetry integration, and health checks.

Long Description

InfinityFlow.Aspire.Temporal is a .NET Aspire integration that makes it easy to add Temporal to your .NET Aspire distributed applications.

Features:

• Run the Temporal CLI dev server as an Aspire container resource with a single line of code
• Automatic connection string resolution via the companion client library
• Built-in OpenTelemetry integration for tracing and metrics
• Health checks for Temporal connectivity
• Configure namespaces, log levels, ports, and dynamic config values directly from the AppHost
• Register workers and clients with minimal boilerplate

Author(s)

Elan Hasson / https://github.com/ElanHasson

[github-actions]

Hi, I'm ZiggyBot! 🤖 Here's my pre-evaluation of this submission:

---

Criterion	Assessment
Useful to Temporal users	✅ Yes — This integration solves a real pain point for .NET Aspire developers by providing a streamlined way to add Temporal's dev server, automatic connection resolution, and observability with minimal boilerplate.
Benefits clearly explained	✅ Yes — The README clearly documents all features including container resource setup, client/worker registration, OpenTelemetry integration, health checks, and comprehensive configuration options with code examples.
OSI Approved License	✅ Yes — The project uses the MIT License, which is OSI approved and the recommended license for Code Exchange submissions.
README with working instructions	✅ Yes — The README provides complete step-by-step instructions with NuGet package installation, AppHost configuration, worker/client registration, and observability setup, including helpful dashboard screenshots.

Overall: Looks good ✅

Notes:

• This is a well-crafted integration that bridges Temporal with the .NET Aspire ecosystem, making distributed application development significantly smoother for .NET developers.
• The project includes a complete sample application demonstrating real-world usage patterns.
• Nice attention to developer experience with fluent configuration APIs that mirror Temporal CLI flags.
• The honest note about container vs. executable resource limitations (linking to relevant GitHub issues) shows good transparency.
• 27 stars and active NuGet publishing indicate community interest and maintenance.
• The inclusion of health checks is a thoughtful production-readiness feature.

Suggested questions for submitter:

• None — the submission is thorough and well-documented.

Teaching moment:

This project demonstrates an excellent pattern for integrating Temporal observability into a larger application framework. The AddTemporalServiceDefaults() method wires up both the Temporal meter and TracingInterceptor activity sources into OpenTelemetry, ensuring distributed tracing flows seamlessly across Workflow and Activity boundaries. This is a great example of how to make Temporal's built-in observability features "just work" within an opinionated application framework, rather than requiring manual configuration each time.
View in source ↗

---

---

ZiggyBot is an AI pre-screener based on Temporal's community mascot Ziggy. Final decisions are made by the community team.

Reviewer: Check the box below to generate a Contentful-ready long description for this submission.

• Generate long description if needed

[github-actions]

Hi, I'm ZiggyBot! 🤖 Here's my pre-evaluation of this submission:

---

Criterion	Assessment
Useful to Temporal users	✅ Yes — This integration significantly reduces boilerplate for .NET Aspire users wanting to run Temporal dev servers, with automatic connection string resolution, OpenTelemetry integration, and health checks built in.
Benefits clearly explained	✅ Yes — The README clearly documents all features with code examples for AppHost configuration, worker registration, client setup, and observability integration, plus helpful screenshots of the Aspire dashboard.
OSI Approved License	✅ Yes — The project uses the MIT License, which is OSI-approved and explicitly recommended.
README with working instructions	✅ Yes — The README provides step-by-step installation instructions, complete code samples for all major use cases, and configuration reference with CLI flag mappings.

Overall: Looks good ✅

Notes:

• This is a well-crafted integration that fills a real gap for .NET developers using Aspire who want to incorporate Temporal into their distributed applications. The 27 stars suggest genuine community interest.
• The project honestly documents a known limitation (executable resource not working as expected) with links to relevant GitHub issues—transparency like this builds trust!
• The fluent configuration API mirrors Temporal CLI flags nicely, making it intuitive for users already familiar with Temporal's dev server options.
• The sample project demonstrates a complete end-to-end setup including worker, API, and AppHost configurations.
• Nice touch including the AddTemporalServiceDefaults() extension for proper OpenTelemetry wiring in service defaults.

Suggested questions for submitter:

• Would you consider adding a brief section about production deployment patterns, or is this integration specifically intended for local development scenarios only?
• The README mentions support for both container and executable resources, but notes only container works—would you like to clarify the current status of executable support in the submission description?

Teaching moment:

This project demonstrates an excellent pattern for integrating Temporal's observability features with .NET's OpenTelemetry ecosystem. The AddTemporalClient and AddTemporalWorker methods automatically register a TracingInterceptor for distributed tracing and set up a CustomMetricMeter for metrics—showing how Temporal's built-in interceptor architecture can be leveraged to plug into broader observability pipelines without requiring manual instrumentation in workflow or activity code. This is a great example of making Temporal's tracing capabilities "just work" in a framework-native way.
View in source ↗

---

---

ZiggyBot is an AI pre-screener based on Temporal's community mascot Ziggy. Final decisions are made by the community team.

Reviewer: Check the box below to generate a Contentful-ready long description for this submission.

• Generate long description if needed