| page_type | languages | products | description | urlFragment | ||
|---|---|---|---|---|---|---|
sample |
|
|
Apps that can be used with as a starting point for some MS Learn Modules. |
Follow the hands-on tutorial to publish a Blazor WebAssembly app and .NET API with Azure Static Web Apps.
This repository contains apps that can be used with as a starting point for some MS Learn Modules.
The shopping theme is used throughout the app.
The apps written in Blazor WebAssembly with a C# Azure Functions API.
- Familiarity with Blazor
- Beginner-level experience with Azure Functions
- A GitHub account
- Node.js LTS and Git
- Visual Studio or Visual Studio Code installed
- The Azure Functions extension installed (if using Visual Studio Code)
- The Azure Functions Core Tools installed (if using Visual Studio Code)
- Learn how to Publish an Angular, React, Svelte, or Vue JavaScript app and API with Azure Static Web Apps
- API support in Azure Static Web Apps
- Add an API to Azure Static Web Apps
- Authentication and authorization
- Routes
- Review pre-production environments
- Learn about the Azure Functions local.settings.json file
- Learn how to Deploy to Azure Using Azure Functions
- Sign up for a Free Trial of Azure
- Azure Free Trial
- VS Code
- VS Code Extension for Node on Azure
- Azure Functions local.settings.json file
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.