Microsoft.Fast.Components.FluentUI 2.0.2

The ID prefix of this package has been reserved for one of the owners of this package by Prefix Reserved
.NET 6.0
There is a newer prerelease version of this package available.
See the version list below for details.
dotnet add package Microsoft.Fast.Components.FluentUI --version 2.0.2
NuGet\Install-Package Microsoft.Fast.Components.FluentUI -Version 2.0.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Microsoft.Fast.Components.FluentUI" Version="2.0.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Microsoft.Fast.Components.FluentUI --version 2.0.2
#r "nuget: Microsoft.Fast.Components.FluentUI, 2.0.2"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install Microsoft.Fast.Components.FluentUI as a Cake Addin
#addin nuget:?package=Microsoft.Fast.Components.FluentUI&version=2.0.2

// Install Microsoft.Fast.Components.FluentUI as a Cake Tool
#tool nuget:?package=Microsoft.Fast.Components.FluentUI&version=2.0.2


License: MIT .NET C# Nuget Nuget

Validate PRs Validate Security

Discord Twitter

⭐ We appreciate your star, it helps!


The Microsoft.Fast.Components.FluentUI package provides a set of Blazor component wrappers around Microsoft's official FluentUI Web Components. The FluentUI Web Components are built on FAST and work in every major browser. To get up and running with Microsoft.Fast.Components.FluentUI see the Getting Started section below.

The source for the library is hosted in the Fast Blazor repository at GitHub. Documentation on the components is available at the demo site and at

The source for @fluentui/web-components is hosted in the Fluent UI mono-repository. Documentation on the components is available on

Getting Started

To get started using the Fluent UI Web Components for Blazor, you will first need to install the official Nuget package for Fluent UI in the project you would like to use the library and components. You can use the following command:

dotnet add package Microsoft.Fast.Components.FluentUI


Next, you need to add the web components script. You can either add the script from CDN directly, or you can install it with NPM, whichever you prefer.

To add the script from CDN use the following markup:

<script type="module" src=""></script>

📓 Note

If you prefer to use another CDN, that is entirely possible. Just make sure it is offering the Fluent UI package and you are getting the right web-components.min.js file)

The markup above always references the latest release of the components. When deploying to production, you will want to ship with a specific version. Here's an example of the markup for that:

<script type="module" src=""></script>

The script tag is normally placed in your index.html (_Layout.cshtml for Blazor server project) file in the script section at the bottom of the <body>.

If you wish to leverage NPM instead, run the following command:

npm install --save @fluentui/web-components

You can locate the single file script build in the following location:


Copy this to your wwwroot/script folder and reference it with a script tag as described above.

📓 Note

If you are setting up Fluent UI Web Components on a Blazor Server project, you will need to escape the @ character by repeating it in the source link. For more information check out the Razor Pages syntax documentation.


In order for this library to work as expected, you will need to add the composed scoped CSS file for the components. This can be done by adding the following line to the <head> section of your index.html or _Layout.cshtml file in the project you installed the package:

<link href="{PROJECT_NAME}.styles.css" rel="stylesheet" /> 

It is possible that the line is already in place (but commented out).


Reboot is a collection of element-specific CSS changes in a single file to help kick-start building a site with the Fluent UI Web Components for Blazor. It provides an elegant, consistent, and simple baseline to build upon.

If you want to use Reboot, you'll need to add to your index.html or _Layout.cshtml file a line that includes the stylesheet (.css file). This can be done by adding the following line to the <head> section:

<link href="_content/Microsoft.Fast.Components.FluentUI/css/reboot.css" rel="stylesheet" />

It is entirely possible to build a site without using Reboot. If you choose not to use it, please do add the variables.css file (which is otherwise imported through the reboot.css file) to your index.html or _Layout.cshtml file in the <head> section like this:

<link href="_content/Microsoft.Fast.Components.FluentUI/css/variables.css" rel="stylesheet" />

The file contains a number of CSS variables that are required to be defined for the components to work correctly.


In your Program.cs file you need to add the following:


This addition makes sure all the necessary services the library uses are setup in a correct way.

Using the FluentUI Web Components

With the package installed and the script configured, you can begin using the Fluent UI Web Components in the same way as any other Blazor component. Just be sure to add the following using statement to your views:

@using Microsoft.Fast.Components.FluentUI

Here's a small example of a FluentCard with a FluentButton that uses the Fluent "Accent" appearance:

@using Microsoft.Fast.Components.FluentUI

  <h2>Hello World!</h2>
  <FluentButton Appearance="@Appearance.Accent">Click Me</FluentButton>

💡 Tip

You can add @using Microsoft.Fast.Components.FluentUI to the namespace collection in _Imports.razor, so you don't have to add it to every razor page that uses one of the components.

Configuring the Design System

The Fluent UI Web Components are built on FAST's Adaptive UI technology, which enables design customization and personalization, while automatically maintaining accessibility. This is accomplished through setting various "Design Tokens". The library exposes all of the (over 160) Design Tokens, which you can use both from code as in a declarative way in your .razor pages. See <a href="" target="_blank"></a> for more information on how Design Tokens work

Option 1: Using Design Tokens from C# code

Given the following .razor page fragment:

<FluentButton @ref="ref1" Appearance="Appearance.Filled">A button</FluentButton>
<FluentButton @ref="ref2" Appearance="Appearance.Filled">Another button</FluentButton>
<FluentButton @ref="ref3" Appearance="Appearance.Filled">And one more</FluentButton>
<FluentButton @ref="ref4" Appearance="Appearance.Filled" @onclick=OnClick>Last button</FluentButton>

You can use Design Tokens to manipulate the styles from C# code as follows:

private BaseLayerLuminance BaseLayerLuminance { get; set; } = default!;

private AccentBaseColor AccentBaseColor { get; set; } = default!;

private BodyFont BodyFont { get; set; } = default!;

private StrokeWidth StrokeWidth { get; set; } = default!;

private ControlCornerRadius ControlCornerRadius { get; set; } = default!;

private FluentButton? ref1;
private FluentButton? ref2;
private FluentButton? ref3;
private FluentButton? ref4;

protected override async Task OnAfterRenderAsync(bool firstRender)
	if (firstRender)
		//Set to dark mode
		await BaseLayerLuminance.SetValueFor(ref1!.Element, (float)0.15);

		//Set to Excel color
		await AccentBaseColor.SetValueFor(ref2!.Element, "#185ABD".ToSwatch());

		//Set the font
		await BodyFont.SetValueFor(ref3!.Element, "Comic Sans MS");

		//Set 'border' width for ref4
		await StrokeWidth.SetValueFor(ref4!.Element, 7);
		//And change conrner radius as well
		await ControlCornerRadius.SetValueFor(ref4!.Element, 15);


public async Task OnClick()
	//Remove the wide border
	await StrokeWidth.DeleteValueFor(ref4!.Element);

As can be seen in the code above (with the ref4.Element), it is possible to apply multiple tokens to the same component.

For Design Tokens that work with a color value, you must call the ToSwatch() extension method on a string value or use one of the Swatch constructors. This makes sure the color is using a format that Design Tokens can handle. A Swatch has a lot of commonality with the System.Drawing.Color struct. Instead of the values of the components being between 0 and 255, in a Swatch they are expressed as a value between 0 and 1.

📓 Note

The Design Tokens are manipulated through JavaScript interop working with an ElementReference. There is no JavaScript element until after the component is rendered. This means you can only work with the Design Tokens from code after the component has been rendered in OnAfterRenderAsync and not in any earlier lifecycle methods.

Option 2: Using Design Tokens as components

The Design Tokens can also be used as components in a .razor page directely. It looks like this:

<BaseLayerLuminance Value="(float?)0.15">
	<FluentCard BackReference="@context">
		<div class="contents">
			<FluentButton Appearance="Appearance.Accent">Accent</FluentButton>
			<FluentButton Appearance="Appearance.Stealth">Stealth</FluentButton>
			<FluentButton Appearance="Appearance.Outline">Outline</FluentButton>
			<FluentButton Appearance="Appearance.Lightweight">Lightweight</FluentButton>

To make this work, a link needs to be created between the Design Token component and its child components. This is done with the BackReference="@context" construct.

📓 Note

Only one Design Token component at a time can be used this way. If you need to set more tokens, use the code approach as described in Option 1 above.

Option 3: Using the <FluentDesignSystemProvider>

The third way to customize the design in Blazor is to wrap the entire block you want to manipulate in a <FluentDesignSystemProvider>. This special element has a number of properties you can set to configure a subset of the tokens. Not all tokens are available/supported and we recommend this to only be used as a fall-back mechanism. The preferred method of working with the design tokens is to manipulate them from code as described in option 1.

Here's an example of changing the "accent base color" and switching the system into dark mode (in the file app.razor):

<FluentDesignSystemProvider AccentBaseColor="#464EB8" BaseLayerLuminance="0">
	<Router AppAssembly="@typeof(App).Assembly">
		<Found Context="routeData">
			<RouteView RouteData="@routeData" DefaultLayout="@typeof(MainLayout)" />
			<PageTitle>Not found</PageTitle>
			<LayoutView Layout="@typeof(MainLayout)">
				<p role="alert">Sorry, there's nothing at this address.</p>

📓 Note

FluentDesignSystemProvider token attributes can be changed on-the-fly like any other Blazor component attribute.

Colors for integration with specific Microsoft products

If you are attempting to configure the components for integration into a specific Microsoft product, the following table provides AccentBaseColor values you can use:

Product AccentBaseColor
Office #D83B01
Word #185ABD
Excel #107C41
PowerPoint #C43E1C
Teams #6264A7
OneNote #7719AA
SharePoint #03787C
Stream #BC1948

For a list of all available token attributes, see here. More examples for other components can be found in the examples folder of this repository.

Blazor Hybrid

Starting with the 2.0 release, you can also use this library in your Blazor Hybrid projects. Setup is almost the same as described in the "Getting started" section above, but to get everything to work you'll need to take two extra steps:

  1. You need to add a MAUI specific IStaticAssetService implementation.
    Due to some issues, this file can't be part of the library (yet) so this needs to be added manually to your MAUI Blazor project.
    Create a new class in you project called FileBasedStaticAssetService.cs Replace it's contents with the following:
using System.Net;
using Microsoft.Fast.Components.FluentUI.Infrastructure;

namespace Microsoft.Fast.Components.FluentUI;

public class FileBasedStaticAssetService : IStaticAssetService
	private readonly CacheStorageAccessor _cacheStorageAccessor;

	public FileBasedStaticAssetService(CacheStorageAccessor cacheStorageAccessor)
		_cacheStorageAccessor = cacheStorageAccessor;

	public async Task<string> GetAsync(string assetUrl, bool useCache = true)
		string result = null;

		HttpRequestMessage message = CreateMessage(assetUrl);

		if (useCache)
			// Get the result from the cache
			result = await _cacheStorageAccessor.GetAsync(message);

		if (string.IsNullOrEmpty(result))
			//It not in the cache (or cache not used), read the asset from disk
			result = await ReadData(assetUrl);

			if (!string.IsNullOrEmpty(result))
				if (useCache)
					// If successful, create the response and store in the cache (when used)
					HttpResponseMessage response = new()
						StatusCode = HttpStatusCode.OK,
						Content = new StringContent(result)

					await _cacheStorageAccessor.PutAsync(message, response);

		return result;

	private static HttpRequestMessage CreateMessage(string url) => new(HttpMethod.Get, url);

	private static async Task<string> ReadData(string file)
		using var stream = await FileSystem.OpenAppPackageFileAsync($"wwwroot/{file}");
		using var reader = new StreamReader(stream);

		return await reader.ReadToEndAsync();
  1. You need to make some changes in your MauiProgram.cs file
    Make sure the following is added before the return builder.Build() line:
builder.Services.AddFluentUIComponents(options =>
		options.HostingModel = BlazorHostingModel.Hybrid;
builder.Services.AddScoped<IStaticAssetService, FileBasedStaticAssetService>();

Use the DataGrid component with EF Core

If you want to use the FluentDataGrid with data provided through EF Core, you need to install an additional package so the grid knows how to resolve queries asynchronously for efficiency. .


Install the package by running the command:

dotnet add package Microsoft.Fast.Components.FluentUI.DataGrid.EntityFrameworkAdapter


In your Program.cs file you need to add the following after the builder.Services.AddFluentUIComponents(); line:


Joining the Community

Looking to get answers to questions or engage with us in real-time? Our community is most active on Discord. Submit requests and issues on GitHub, or join us by contributing on some good first issues via GitHub.

If you don't find a component you're looking for, it's best to create the issue in our FAST repo here and limit issues on this repo to bugs in the Blazor component wrappers or Blazor-specific features.

We look forward to building an amazing open source community with you!


  • Join the community and chat with us in real-time on Discord.
  • Submit requests and issues on GitHub.
  • Contribute by helping out on some of our recommended first issues on GitHub.
Product Versions
.NET net6.0 net6.0-android net6.0-ios net6.0-maccatalyst net6.0-macos net6.0-tvos net6.0-windows net7.0 net7.0-android net7.0-ios net7.0-maccatalyst net7.0-macos net7.0-tvos net7.0-windows
Compatible target framework(s)
Additional computed target framework(s)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (5)

Showing the top 5 NuGet packages that depend on Microsoft.Fast.Components.FluentUI:

Package Downloads

Application Component for the Alliance Business Suite.


Base components to built UI in Blazor.


Package Description

Microsoft.Fast.Components.FluentUI.DataGrid.EntityFrameworkAdapter The ID prefix of this package has been reserved for one of the owners of this package by

An adapter for using the Fluent UI Blazor DataGrid with Entity Framework.


Package Description

GitHub repositories (4)

Showing the top 4 popular GitHub repositories that depend on Microsoft.Fast.Components.FluentUI:

Repository Stars
A library to support tests with throwaway instances of Docker containers for all compatible .NET Standard versions.
Blazor component library for FluentUI. Microsoft's official wrapper around the FluentUI Web Components for use with .NET 6.0 or higher Blazor applications
OpenAPI based HTTP Client code generator
Project Phalanx is a roster editor handling BattleScribe datafiles
Version Downloads Last updated
2.1.0-beta-1 127 1/24/2023
2.0.2 637 1/25/2023
2.0.1 1,484 1/10/2023
2.0.0 607 1/6/2023
2.0.0-rc-2 395 12/21/2022
2.0.0-rc-1 222 11/30/2022
1.6.0 6,653 11/8/2022
1.5.3 11,123 9/12/2022
1.5.2 11,392 9/6/2022
1.5.1 12,791 8/19/2022
1.5.0 29,523 7/18/2022
1.4.4 64,295 6/10/2022
1.4.3 545 6/7/2022
1.4.2 46,250 6/2/2022
1.4.1 108,284 5/11/2022
1.4.0 1,885 4/26/2022
1.3.1 467 4/25/2022
1.3.0 1,007 4/18/2022
1.2.1 793 4/12/2022
1.2.0 2,197 3/23/2022
1.1.0 13,293 12/3/2021
1.0.0 7,774 11/9/2021
0.5.0 304 10/29/2021
0.4.0 3,977 10/7/2021
0.3.0 2,458 8/5/2021
0.2.0 5,854 5/24/2021
0.1.0 394 5/6/2021
0.0.4 295 5/5/2021
0.0.3 283 5/5/2021
0.0.2 302 5/5/2021