Although we have created a quite complete port of the React Fluent UI library, it has become clear that it is impossible for us to keep up with the changes that Microsoft and the community are making there. That, combined with the fact that we have only a few people working on the code (in their spare time mostly), has made us decide that as of now we will be switching to maintenace mode for the BlazorFluentUI library.
We will not be adding any new functionality and bug fixing will be minimal.
That is up to you. The functionality and features that are available will stay available. We have released a V6 version, running on .NET 6. This means you can still use the library in it's current form until at least November 2022 (when .NET 7 will be released). Maybe we will even release a verion compiled on that .NET version, but no promises.
Microsoft has released V1.0 of a Blazor wrapper (https://github.com/microsoft/fast-blazor) for their Fluent UI Web Components library based on standard Web Components technology (https://github.com/microsoft/fluentui/blob/master/packages/web-components/README.md) which is an implementation of their FAST framework (https://www.fast.design/). We are in close contact with the Microsoft team, leveraging our knowledge gained with building BlazorFluentUI and are already actively contributing to the repository. Their not aiming to match what you get with React Fluent UI today. Rather, they are building to the latest version of Fluent as seen in Windows 11. An implementation of all the current Fluent Web Components can be found at https://aka.ms/fluentwebcomponents. An official Blazor demo environment is in the works too. For now you can visit https://fluentui-blazor.baaijte.net/
Port of Fluent UI React components and style (formerly Office Fabric) to Blazor
https://www.blazorfluentui.net/
https://blazorfluentui.azurewebsites.net/ (Older version!)
Installation
How To Use: Blazor Webassembly
How To Use: Blazor Server
Theming
Using the .NET 6 released packages now.
Breaking Changes!
Icons are now sourced from the MIT licensed FluentUI Icons repo (https://github.com/microsoft/fluentui-system-icons). These are embedded within the CoreComponents project. Icon names are now all "snakecase" (lowercase with underscores). Some of the icon names are completely different. You can either visit the repo linked or see this demo's Icons page. FontSize is an additional option for Icon which is largely irrelevant unless you modify the size using css. However, Filled is a unique option that chooses the filled version of the icon, if it exists. You no longer need to reference the fabric.min.css file in your index.html page.
IDropdownOption (and therefore DropdownOption) is extended to implement IComparable. This makes it possible to sort on selected dropdown values in a details list.
- Added parameter
DropdownHeightto limit the height of the dropdownlist. See first sample on https://www.blazorfluentui.net/dropdownPage for usage (also showing DropdownWidth)
- DetailsList and DetailsListAuto speed vastly improved
- Callout no longer tracking references in script. No more double clicking needed for opening Dropdown, etc.
TextFieldNumberis renamed toNumericTextFieldMaskedTextFiledis now available as a BETA component. See https://www.blazorfluentui.net/MaskedTextFieldPage for examples
- Library is now using JavaScript isolation (see https://docs.microsoft.com/en-us/aspnet/core/blazor/call-javascript-from-dotnet?view=aspnetcore-5.0#blazor-javascript-isolation-and-object-references). No longer needed to reference the scripts in your
_Host.cshtml/index.html! (with exception of the still experimental RichTextEditor script and acompanying Quill library). Blazor Server in .NET 5.0 no longer supports IE11/Legacy edge so neither does the demo.
- Add editable column for
DetailsList, DetailsListAuto - Add new component
TextFieldNumber(will be renamed to NumberTextField soon), based onTextField. Supportsint, long, short, float, double and decimal. See https://www.blazorfluentui.net/TextFieldNumberPage for examples
We dropped the BFU prefix from all the component- and project names. Also, all components are now bundled in only two packages (to make a distinction between components dependant on DynamicData package an those who are not).
In cases where renaming would lead to collisions with already existing Blazor components or .NET classes, we placed those components in seperate namespace (which you need to include explicitly) and/or you need to use the full name of the component (so including the namespace) in your .razor files.
Both changes were made to align the library closer to the Fluent UI React environment. Also the codebase is not so cluttered with 'BFU' anymore.
The demo sites have been given a lot of attention and look a lot better now (more in line with Fluent UI Rect docs).
Library is now running on .NET 5
You will now have to define your list's container separately from the list component. Pick a <div> or other container element and apply the data-is-scrollable to it. You'll also have to style it appropriately for your page. (For example, add overflow-y:auto;height:100%; or something similar.) You do not have to place your list component as a direct descendant of this container. If you fail to place the data-is-scrollable tag, then the component will traverse the nodetree to find the first container element that has overflow-y:auto; set.
You also have to define GetKey for your list component. This is a selector for your items to tell the component how to uniquely identify each item.
A big change is that OnItemInvoked will only work when SelectionMode is set to None. If you need Selection active and the invoke item function to work at the same time, you can attach an event handler to the Selection.OnSelelectionChanged event or subscribe to the SelectionChanged observable.
These components and interfaces must be removed as they no longer function within this library. Switch to using CSS isolation with your razor components instead. BFULocalCS is still present and encouraged for dynamic styling that requires flexibility. (Using the style attribute on an element makes it difficult for users to override the style.)
If you need to reference the theme from a css file, you can reference the global css variable instead. For example, where before you would get a white color in C# as Theme.Palette.White, now you will write in css, var(--palette-White). Css global variables always start with two dashes and a lowercase name. Instead of a dot, use a dash followed by capitalized names.
There are no MergeStyles in this port. It's just each control packaged into its own project so you can limit what gets added to your Blazor project.
On each commit new dev NuGet packages will be created automatically. To access those, add a new Package Source to Visual Studio or your project with the following URL:
https://pkgs.dev.azure.com/blazor-fluentui/5355f597-190a-4424-83da-cd89cd362a24/_packaging/DevChannelV5/nuget/v3/index.json
For a more detailed tutorial, head over to our Public Feed, click on "Connect To Feed" and select the platform.