Dev integrations

    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

    This document assumes that you’re building a production application, and want to create a repeatable and robust set of development practices. The guidance here is general, and applies to any .NET server application using Dapr (including actors).

    • 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.

    Choose one of these links to learn about tools you can use in local development scenarios. These articles are ordered from lowest investment to highest investment. You may want to read them all to get an overview of your options.

    Dapr .NET SDK Development with Dapr CLI
    Dapr .NET SDK Development with Project Tye

    Learn about local development with Project Tye

    Dapr .NET SDK Development with Docker-Compose

    Learn about local development with Docker-Compose