<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>C# on Joe Stead</title><link>https://joestead.codes/tags/c%23/</link><description>Recent content in C# on Joe Stead</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Tue, 02 Jun 2026 22:13:59 +0100</lastBuildDate><atom:link href="https://joestead.codes/tags/c%23/index.xml" rel="self" type="application/rss+xml"/><item><title>Testing and Configuration in .NET Core</title><link>https://joestead.codes/posts/testing-with-configuration-dotnet/</link><pubDate>Tue, 04 Aug 2020 17:00:00 +0100</pubDate><guid>https://joestead.codes/posts/testing-with-configuration-dotnet/</guid><description>&lt;p&gt;When running automated tests, or running things locally, I often want to use a different configuration to what I would run in production. A JSON file often suffices for local development, however this isn&amp;rsquo;t useful for automated tests where I want different configurations for different tests, or if my configuration is dynamic (e.g. I need to spin up a docker container during startup, and I have to get some configuration from that on the fly).&lt;/p&gt;</description></item></channel></rss>