Aspire

When you build Azure Functions apps with Aspire, the best experience is usually the one where the AppHost reflects intent instead of infrastructure plumbing.

That matters a lot with Durable Task Scheduler. In a local dev loop, I want an emulator. In Azure, I want the real resource. The recent Aspire integration makes that split much cleaner than the older manual approach.

Aspire 13.3 introduced support for Durable Task Scheduler as part of the Azure Functions integration.

If you’re building modern .NET Aspire apps, you’re probably familiar with how service names and resource identifiers are often passed around as string literals, things like "apiservice" or "storage".