Developing applications with the Dapr .NET SDK

Using your favorite IDE or editor to launch an application typically assumes that you only need to run one thing - the application you are debugging. However, developing microservices challenges you think about your local development process for more than one at a time. A microservices application has multiple services that you might need running at the same time as well as dependencies like state stores to manage.

Adding Dapr to your development process means you need to manage the following concerns:

• Each service you want to run
• Dapr component and configuration manifests
• Additional dependencies such as state stores
• optional: the Dapr placement service for actors

You have two primary methods of storing component definitions for local development with Dapr:

• Use your own location

Creating a folder within your source code repository to store components and configuration will give you a way to version and share these definitions. The guidance provided here will assume you created a folder next to the application source code to store these files.

Learn about local development with the Dapr CLI

Learn about local development with Project Tye