Blazor preview documentation
Blazor is an unsupported experimental web framework that shouldn't be used for production workloads at this time.
Blazor is a new experimental .NET web framework using C#/Razor and HTML that runs in the browser with WebAssembly.
Explore Blazor preview documentation
Build your first Blazor app
Build a Blazor app step-by-step and quickly learn the basic features of the Blazor framework.
Frequently asked questions (FAQ)
Find the answers to frequently asked questions about Blazor.
Introduction to Blazor
Discover how Blazor runs in the browser to execute C#/Razor code with WebAssembly and the .NET runtime.
Create and use Blazor components, the fundamental building blocks of Blazor apps provided by compiled Razor or C# files.
Learn how to create reusable layout components for Blazor apps.
See how Blazor apps can use built-in services by having them injected into components.
Learn how to route requests in a client-side Blazor app and about the NavLink component.
Host and deploy
Discover how to host and deploy Blazor apps using hosted and standalone deployment models.
Suggest a feature or file a bug report
Contribute to the Blazor documentation
Blazor preview documentation is provided to assist you in trying out Blazor. We need your help to improve the documentation. For instructions, see Contributing to the Blazor documentation.
Blazor release notes
View and download samples
Several topics show source code and samples that are available to view or download from GitHub. To view a sample, follow the sample link. To download the code, follow these instructions:
- Download the repository that contains the sample code by performing one of the following procedures:
- Download a ZIP of the repository to your local system. Un-ZIP the compressed archive.
- Fork the repository and clone the fork to your local system. Forking and cloning permits you to make contributions to the documentation by committing changes to your fork and then creating a pull request for the docs repository. For more information, see the .NET Documentation Contributing Guide and the ASP.NET Docs Contributing Guide.
- Clone the repository locally. If you clone a docs repository directly to your local system, you won't be able to make commits directly against the repository, so you won't be able to make documentation contributions later. Use the fork and clone procedure previously described if you want to preserve the opportunity to contribute to the documentation later.
- Navigate within the repository's folders to the sample's location. The relative path to the sample's location appears in your browser's address bar when you follow the link to the sample in your browser.
- To run a sample, you have several options:
- Use the .NET CLI tools: In a console window, navigate to the sample's folder and use dotnet CLI commands.
- Use Visual Studio or Visual Studio for Mac: Open the sample by selecting File > Open > Project/Solution from the menu bar, navigate to the sample project folder, and select the project file (*.csproj or *.fsproj).
- Use Visual Studio Code: Open the sample by selecting File > Open Folder from the menu bar and selecting the sample's project folder.
- Use a different IDE that supports .NET Core projects.