<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developing applications with the Dapr .NET SDK on Dapr Docs</title><link>https://v1-18.docs.dapr.io/developing-applications/sdks/dotnet/dotnet-integrations/</link><description>Recent content in Developing applications with the Dapr .NET SDK on Dapr Docs</description><generator>Hugo</generator><language>en</language><atom:link href="https://v1-18.docs.dapr.io/developing-applications/sdks/dotnet/dotnet-integrations/index.xml" rel="self" type="application/rss+xml"/><item><title>Dapr .NET SDK Development with Dapr CLI</title><link>https://v1-18.docs.dapr.io/developing-applications/sdks/dotnet/dotnet-integrations/dotnet-development-dapr-cli/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/developing-applications/sdks/dotnet/dotnet-integrations/dotnet-development-dapr-cli/</guid><description>&lt;h2 id="dapr-cli">Dapr CLI&lt;/h2>
&lt;p>&lt;em>Consider this to be a .NET companion to the &lt;a href="https://v1-18.docs.dapr.io/operations/hosting/self-hosted/self-hosted-with-docker/">Dapr Self-Hosted with Docker Guide&lt;/a>&lt;/em>.&lt;/p>
&lt;p>The Dapr CLI provides you with a good base to work from by initializing a local redis container, zipkin container, the placement service, and component manifests for redis. This will enable you to work with the following building blocks on a fresh install with no additional setup:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://v1-18.docs.dapr.io/developing-applications/building-blocks/service-invocation/">Service invocation&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://v1-18.docs.dapr.io/developing-applications/building-blocks/state-management/">State Store&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://v1-18.docs.dapr.io/developing-applications/building-blocks/pubsub/">Pub/Sub&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://v1-18.docs.dapr.io/developing-applications/building-blocks/actors/">Actors&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can run .NET services with &lt;code>dapr run&lt;/code> as your strategy for developing locally. Plan on running one of these commands per-service in order to launch your application.&lt;/p></description></item><item><title>Dapr .NET SDK Development with Docker-Compose</title><link>https://v1-18.docs.dapr.io/developing-applications/sdks/dotnet/dotnet-integrations/dotnet-development-docker-compose/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/developing-applications/sdks/dotnet/dotnet-integrations/dotnet-development-docker-compose/</guid><description>&lt;h2 id="docker-compose">Docker-Compose&lt;/h2>
&lt;p>&lt;em>Consider this to be a .NET companion to the &lt;a href="https://v1-18.docs.dapr.io/operations/hosting/self-hosted/self-hosted-with-docker/">Dapr Self-Hosted with Docker Guide&lt;/a>&lt;/em>.&lt;/p>
&lt;p>&lt;code>docker-compose&lt;/code> is a CLI tool included with Docker Desktop that you can use to run multiple containers at a time. It is a way to automate the lifecycle of multiple containers together, and offers a development experience similar to a production environment for applications targeting Kubernetes.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Pro:&lt;/strong> Since &lt;code>docker-compose&lt;/code> manages containers for you, you can make dependencies part of the application definition and stop the long-running containers on your machine.&lt;/li>
&lt;li>&lt;strong>Con:&lt;/strong> most investment required, services need to be containerized to get started.&lt;/li>
&lt;li>&lt;strong>Con:&lt;/strong> can be difficult to debug and troubleshoot if you are unfamilar with Docker.&lt;/li>
&lt;/ul>
&lt;h3 id="using-docker-compose">Using docker-compose&lt;/h3>
&lt;p>From the .NET perspective, there is no specialized guidance needed for &lt;code>docker-compose&lt;/code> with Dapr. &lt;code>docker-compose&lt;/code> runs containers, and once your service is in a container, configuring it similar to any other programming technology.&lt;/p></description></item><item><title>Dapr .NET SDK Development with .NET Aspire</title><link>https://v1-18.docs.dapr.io/developing-applications/sdks/dotnet/dotnet-integrations/dotnet-development-dapr-aspire/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/developing-applications/sdks/dotnet/dotnet-integrations/dotnet-development-dapr-aspire/</guid><description>&lt;h1 id="net-aspire">.NET Aspire&lt;/h1>
&lt;p>&lt;a href="https://learn.microsoft.com/dotnet/aspire/get-started/aspire-overview">.NET Aspire&lt;/a> is a development tool
designed to make it easier to include external software into .NET applications by providing a framework that allows
third-party services to be readily integrated, observed and provisioned alongside your own software.&lt;/p>
&lt;p>Aspire simplifies local development by providing rich integration with popular IDEs including
&lt;a href="https://visualstudio.microsoft.com/vs/">Microsoft Visual Studio&lt;/a>,
&lt;a href="https://code.visualstudio.com/">Visual Studio Code&lt;/a>,
&lt;a href="https://blog.jetbrains.com/dotnet/2024/02/19/jetbrains-rider-and-the-net-aspire-plugin/">JetBrains Rider&lt;/a> and others
to launch your application with the debugger while automatically launching and provisioning access to other
integrations as well, including Dapr.&lt;/p></description></item></channel></rss>