
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Dan Does Code</title>
      <link>https://www.dandoescode.com/blog</link>
      <description>A blog about .NET and Software Architecture</description>
      <language>en-us</language>
      <managingEditor>me@dandoescode.com (Daniel Mackay)</managingEditor>
      <webMaster>me@dandoescode.com (Daniel Mackay)</webMaster>
      <lastBuildDate>Fri, 22 May 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.dandoescode.com/tags/testing/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.dandoescode.com/blog/dotnet-aspire-configuration-guide</guid>
    <title>Aspire - Where should the configuration live? A Decision Framework</title>
    <link>https://www.dandoescode.com/blog/dotnet-aspire-configuration-guide</link>
    <description>A modular monolith with Aspire, integration tests, and a real deployment ends up with config scattered across appsettings, user-secrets, env vars, and Key Vault. Here&#39;s the framework I use to decide where each value belongs, and why putting things in the wrong layer always burns you eventually.</description>
    <pubDate>Fri, 22 May 2026 00:00:00 GMT</pubDate>
    <author>me@dandoescode.com (Daniel Mackay)</author>
    <category>dotnet</category><category>aspire</category><category>architecture</category><category>devops</category><category>testing</category>
  </item>

    </channel>
  </rss>
