During this workshop we're going to write Azure Functions in C# (.NET Core). The goal of this lab is to very that the required SDKs, IDE and tooling are installed.
Verify that you have a recent .NET Core SDK installed:
- .NET Core SDK (at least 3.1). Check with typing
dotnet --list-sdksin the console. - .NET Core SDKs can be downloaded here.
Verify that you have an IDE with extension/plugins for Azure Functions:
- VS 2019 with Azure development workload
- VS Code with Azure Functions extension
- Jetbrains Rider 2019 with the Azure Toolkit Plugin
Azure Functions Core Tools (which includes the local Azure Function Runtime) should be part of the above IDE's and extensions. It could however that these extensions are outdated. Ensure you're using the latest version of the extensions/toolkit (you can usually upgrade within your IDE). I'm currently running version 3.0.2245.
In case you need to install the latest Azure Functions Core Tools manually please follow these instructions.
Verify that you have these tools installed in order to run Azure Functions locally:
- Storage Emulator (Windows only)
- When you're not using a Windows machine you need to create a Storage Account in Azure instead.
- Azure Storage Explorer
- VS Code + REST Client or Postman in order to make HTTP requests.
Although most of the labs can be done completely locally (when running Windows) it would be fun if you could deploy your Function App to Azure in the final labs. For this you require:
- An Azure account.
- The Azure CLI to create the Azure resources (or you can use the Azure portal to create these).
If you're not running Windows you need an Azure Storage Account which requires an Azure account.
Completely optional but still useful:
- I have made some code snippets, which can speed up the process (and prevent mistakes) when creating client, orchestrator and activity functions.
Now let's move on to the next lab to create a new Azure Function app.