<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Durable-Task-Scheduler on Michael S. Collier</title>
    <link>/tags/durable-task-scheduler/</link>
    <description>Recent content in Durable-Task-Scheduler on Michael S. Collier</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Michael S. Collier</copyright>
    <lastBuildDate>Sun, 14 Jun 2026 17:32:11 -0400</lastBuildDate>
    <atom:link href="/tags/durable-task-scheduler/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using Durable Task Scheduler with Aspire</title>
      <link>/using-durable-task-scheduler-with-aspire/</link>
      <pubDate>Sun, 14 Jun 2026 00:00:00 +0000</pubDate>
      <guid>/using-durable-task-scheduler-with-aspire/</guid>
      <description>&lt;p&gt;When you build Azure Functions apps with Aspire, the best experience is usually the one where the AppHost reflects intent instead of infrastructure plumbing.&lt;/p&gt;&#xA;&lt;p&gt;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.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://aspire.dev/whats-new/aspire-13-3/#durable-task-scheduler-for-azure-functions&#34;&gt;Aspire 13.3&lt;/a&gt; introduced support for Durable Task Scheduler as part of the Azure Functions integration.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
