https://gabrielmongeon.ca/en/tags/orchestration/Recent content in Orchestration on Gabriel MongeonHugoenFri, 26 Jun 2026 00:00:00 -0400https://gabrielmongeon.ca/en/2026/06/orchestrate-blazor-ollama-with-aspire/Fri, 26 Jun 2026 00:00:00 -0400https://gabrielmongeon.ca/en/2026/06/orchestrate-blazor-ollama-with-aspire/<blockquote> <p>Part 5 in the &ldquo;Local AI with Ollama and .NET&rdquo; series: <a href="https://gabrielmongeon.ca/en/2025/12/local-ai-development-ollama-dotnet/">Part 1 – Ollama and .NET</a> | <a href="https://gabrielmongeon.ca/en/2025/12/local-rag-ollama-litellm-qdrant/">Part 2 – Local RAG</a> | <a href="https://gabrielmongeon.ca/en/2025/12/ai-agents-ollama-dotnet/">Part 3 – AI Agents</a> | <a href="https://gabrielmongeon.ca/en/2026/02/mcp-csharp-weather-server/">Part 3.5 – MCP Server</a> | <a href="https://gabrielmongeon.ca/en/2026/03/microsoft-agent-framework-ollama-mcp/">Part 4 – Microsoft Agent Framework</a> | <a href="https://gabrielmongeon.ca/2026/06/orchestrer-blazor-ollama-avec-aspire/">Version française</a></p></blockquote> <p>Through the rest of the series, Ollama ran by hand: installed locally on the machine, the <code>ollama pull</code> done manually, and the .NET app pointing at Ollama&rsquo;s local address hardcoded. It works, but it&rsquo;s several manual steps to repeat on every machine. Aspire takes care of this configuration. I wanted to see what it changes.</p>