↓ Skip to main content
  1. Series/

Aspire Field Notes: A Better Developer Loop

An application can start cleanly and still fail its first useful request. This series follows a catalog lookup through that gap: reproducing a 503, keeping the trace, investigating the dependency, and checking the same path after a change.

Aspire Field Notes uses Aspire 13.6 and one small catalog app throughout. The posts explain what to look for; the companion walkthroughs provide setup and commands.

The reading path
#

PartPostWhat you will do
1Stop Losing the Bug When You Restart AspirePreserve a failure, compare diagnostic runs, and understand what the dashboard actually retains
2A Polyglot App Is More Than a Process ListConnect configuration, readiness, and telemetry across languages, including the new Java and Rust hosting previews

More parts are coming soon.

The application behind the examples
#

The code lives in the aspire-field-notes collection in blog-samples. The catalog has a Vite frontend named web, a catalog API named api, PostgreSQL’s catalogdb, and a separate inventory service.

A development-only inventory fault makes /api/catalog return a 503 while resource health remains green. The /api/state endpoints let us save a note through DATA_PATH and read it after a restart. Both are local teaching examples.

Part three also has an independent Node terminal AppHost. Part six publishes Docker Compose files for review without building images or deploying. Express, Sandboxes, and the other cloud targets are comparisons with their documentation.

Companion walkthroughs
#

PartWalkthrough
1Baseline, failure, retained run, and recovery
2Configuration, readiness, and telemetry across the catalog app

Start with the collection README for prerequisites, the clone command, and the one-time database secret. The current companion baseline is Aspire CLI, AppHost SDK, and stable integrations 13.6.4. The README also shows how to update both sample AppHosts with aspire update; upgrading the installed CLI does not change project package references.

Use Load catalog on web in the dashboard, or aspire resource web load-catalog, to make the request and get its status and trace ID. The other helpers check state after a restart, fresh terminal output, and generated Compose routing and storage. None requires installing agent guidance.

The official Node.js weather-map sample is an additional example of a frontend, instrumented API, and external dependency under a TypeScript AppHost. The Java and Rust sections explain optional preview integrations; those languages are not required to run the catalog companion.

Aspire 13.6.4 is the current patch baseline. It improves resource-creation timeout recovery, fixes TypeScript publishing with parameterized Azure enum properties, and restricts CLI diagnostic logs to owner-only permissions on Unix. The earlier 13.6.2 and 13.6.3 patches include a MessagePack security update and resource-watch reliability fixes. The posts identify preview packages and experimental APIs as they come up. The companion keeps stable AddProject resources; there’s no Project V2 migration or Azure deployment to perform.

What this builds on
#

My earlier CLI introduction and deployment article cover the original command-oriented journey. The MCP article and skills, plugins, and marketplace guide explain the agent-tooling background.

Those articles reflect their publication versions. This series uses the 13.6 documentation for current commands and behavior, particularly the move to skills-first agent setup with optional MCP.

Sources worth exploring
#

2026

Put the Debugging Tools Next to the App

Put the Debugging Tools Next to the App

·1919 words·10 mins
The catalog looks wrong. Before changing the API, you want to answer a smaller question: are the expected products actually in its database? Logs tell you what the application reported. A database query lets you inspect the stored rows directly. Aspire 13.6.4 can open an opt-in PostgreSQL client beside the dashboard, without making you find a port, install psql, or copy a password.
A Polyglot App Is More Than a Process List

A Polyglot App Is More Than a Process List

Starting a frontend, an API, and a database is straightforward. Knowing which address each process should use, when its dependencies are ready, and where a failed request went is the harder part. In the catalog companion, Load catalog can return HTTP 503 while the API and inventory service both report healthy. Nothing has to crash for the application to fail.
Stop Losing the Bug When You Restart Aspire

Stop Losing the Bug When You Restart Aspire

··1951 words·10 mins
You reproduce an intermittent failure, change one line, and restart the application. This time the request works. Now you need the old trace to work out why. If it disappeared with the restart, you’re left comparing the new run with whatever you remember. Aspire 13.6’s dashboard keeps completed runs, so you can go back to the failed request instead.1