This is the repository for the LinkedIn Learning course Azure Dapr for .NET Developers Part 1. The full course is available from LinkedIn Learning.
Azure Dapr can help .NET developers solve several challenges that they face when building distributed applications. In this course, Rodrigo Díaz Concha shows you how to build distributed applications and microservices easily with Dapr. Rodrigo begins by introducing Dapr as a portable, event-driven runtime for creating distributed applications in the cloud. He explains the sidecar pattern and the different components and tools that you will use in Dapr. Rodrigo walks you through preparing your development environment, then covers some of the most important building blocks in Dapr. This course focuses on publish and subscribe (pub/sub), service invocation, state management, and bindings.
This repository has branches for each of the videos in the course. You can use the branch pop up menu in github to switch to a specific branch and take a look at the course at that stage, or you can add /tree/BRANCH_NAME to the URL to go to the branch you want to access.
The branches are structured to correspond to the videos in the course. The naming convention is CHAPTER#_MOVIE#. As an example, the branch named 02_03 corresponds to the second chapter and the third video in that chapter.
Some branches will have a beginning and an end state. These are marked with the letters b for "beginning" and e for "end". The b branch contains the code as it is at the beginning of the movie. The e branch contains the code as it is at the end of the movie. The main branch holds the final state of the code when in the course.
When switching from one exercise files branch to the next after making changes to the files, you may get a message like this:
error: Your local changes to the following files would be overwritten by checkout: [files]
Please commit your changes or stash them before you switch branches.
Aborting
To resolve this issue:
Add changes to git using this command: git add .
Commit changes using this command: git commit -m "some message"
Rodrigo Díaz Concha
Check out my other courses on LinkedIn Learning.