<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Stuart Dobson - AI Developer &amp; Systems Builder</title><link>https://stuartdobson.net/blog/</link><description>Recent content in Blog on Stuart Dobson - AI Developer &amp; Systems Builder</description><generator>Hugo</generator><language>en-au</language><lastBuildDate>Sat, 01 Mar 2025 10:00:00 +1100</lastBuildDate><atom:link href="https://stuartdobson.net/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Agent2Agent (A2A): The Other Protocol .NET Architects Need to Know</title><link>https://stuartdobson.net/blog/a2a-protocol-architecture/</link><pubDate>Sat, 01 Mar 2025 10:00:00 +1100</pubDate><guid>https://stuartdobson.net/blog/a2a-protocol-architecture/</guid><description>&lt;p>MCP tells your agent how to use a tool. A2A tells your agent how to talk to another agent.&lt;/p>
&lt;p>It&amp;rsquo;s very early days on the .NET implementation but I managed to get a quick proof of concept working which gave me a good feel for the new protocol.&lt;/p>
&lt;p>This post covers what A2A is, how it differs from MCP, what the current .NET support looks like, and how to design your systems today so that A2A adoption later is an incremental step rather than a rearchitecture.&lt;/p></description></item><item><title>Building Your First AI-Powered .NET Application</title><link>https://stuartdobson.net/blog/building-first-ai-dotnet-app/</link><pubDate>Mon, 10 Feb 2025 10:00:00 +1100</pubDate><guid>https://stuartdobson.net/blog/building-first-ai-dotnet-app/</guid><description>&lt;p>Many organisations are exploring AI but don&amp;rsquo;t know where to start with actual implementation. This guide walks through building a production-ready AI feature in a .NET application using Azure OpenAI.&lt;/p>
&lt;h2 id="why-azure-openai-for-net-developers">Why Azure OpenAI for .NET Developers&lt;/h2>
&lt;p>Azure OpenAI provides enterprise-grade AI capabilities with familiar .NET tooling, Azure AD authentication, and compliance features Australian businesses require. Unlike direct OpenAI API access, you get:&lt;/p>
&lt;ul>
&lt;li>Data residency in Australian datacentres&lt;/li>
&lt;li>Azure&amp;rsquo;s security and compliance frameworks&lt;/li>
&lt;li>Integration with existing Azure infrastructure&lt;/li>
&lt;li>Cost management and monitoring through Azure Portal&lt;/li>
&lt;/ul>
&lt;h2 id="setting-up-your-environment">Setting Up Your Environment&lt;/h2>
&lt;p>First, provision an Azure OpenAI resource in your Azure subscription. You&amp;rsquo;ll need:&lt;/p></description></item><item><title/><link>https://stuartdobson.net/blog/output/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://stuartdobson.net/blog/output/</guid><description>&lt;p>Many organisations are exploring AI but don’t know where to start
with actual implementation. This guide walks through building a
production-ready AI feature in a .NET application using Azure
OpenAI.&lt;/p>
&lt;h2 id="why-azure-openai-for-.net-developers">Why Azure OpenAI for .NET
Developers&lt;/h2>
&lt;p>Azure OpenAI provides enterprise-grade AI capabilities with familiar
.NET tooling, Azure AD authentication, and compliance features
Australian businesses require. Unlike direct OpenAI API access, you
get:&lt;/p>
&lt;ul>
&lt;li>Data residency in Australian datacentres&lt;/li>
&lt;li>Azure’s security and compliance frameworks&lt;/li>
&lt;li>Integration with existing Azure infrastructure&lt;/li>
&lt;li>Cost management and monitoring through Azure Portal&lt;/li>
&lt;/ul>
&lt;h2 id="setting-up-your-environment">Setting Up Your Environment&lt;/h2>
&lt;p>First, provision an Azure OpenAI resource in your Azure subscription.
You’ll need:&lt;/p></description></item></channel></rss>