Blazor Starter Application
This template contains an example .NET 6 Blazor WebAssembly client application, a .NET 6 C# Azure Functions, and a C# class library with shared code.
Getting Started
-
Create a repository from the GitHub template and then clone it locally to your machine.
-
In the Api folder, copy
local.settings.example.json
tolocal.settings.json
-
Continue using either Visual Studio or Visual Studio Code.
Visual Studio 2022
Once you clone the project, open the solution in Visual Studio 2022 and follow these steps:
-
Right-click on the solution and select Set Startup Projects....
-
Select Multiple startup projects and set the following actions for each project:
- Api - Start
- ApiIsolated - None
- Client - Start
- Shared - None
-
Press F5 to launch both the client application and the Functions API app.
Visual Studio Code with Azure Static Web Apps CLI
-
Install the Azure Static Web Apps CLI and Azure Functions Core Tools CLI.
-
Open the folder in Visual Studio Code.
-
In the VS Code terminal, run the following command to start the Static Web Apps CLI, along with the Blazor WebAssembly client application and the Functions API app:
swa start http://localhost:5000 --run "dotnet run --project Client/Client.csproj" --api-location Api
The Static Web Apps CLI (
swa
) first starts the Blazor WebAssembly client application and connects to it at port 5000, and then starts the Functions API app. -
Open a browser and navigate to the Static Web Apps CLI's address at
http://localhost:4280
. You'll be able to access both the client application and the Functions API app in this single address. When you navigate to the "Fetch Data" page, you'll see the data returned by the Functions API app. -
Enter Ctrl-C to stop the Static Web Apps CLI.
Template Structure
- Client: The Blazor WebAssembly sample application
- Api: A C# Azure Functions API, which the Blazor application will call
- Shared: A C# class library with a shared data model between the Blazor and Functions application
- ApiIsolated: A C# Azure Functions API using the .NET isolated execution model, which the Blazor application will call. This version can be used instead of the in-process function app in
Api
.
Deploy to Azure Static Web Apps
This application can be deployed to Azure Static Web Apps, to learn how, check out our quickstart guide.