v5 RC testing by a novice

[bdelaney]

I'm a retired dev. Mostly MS stack. I used Blazor WASM to build a hobby site 3+ years ago. It was a 2 day effort based on a CodeSpace project. Used a little Bootstrap. No complex components. It's been idling, still working, but it was always just a quick hack. I decided last week to level it up.

After much research and a little testing with other UI kits, I want to move to FluentUI. I did a basic test site locally using release 4.14. Then I upgraded the test site to the RC after installing with this command:
dotnet add package Microsoft.FluentUI.AspNetCore.Components --version 5.0.0-rc.1-26048.1

I spent a day working through a bunch of breaking changes. But at the end I was frustrated to find that the site would not run in debug mode on my local machine. Dead end. That was a week ago and I've now got a new test site running on the current version and I'm publishing it to GitHub Pages without issue.

But I thought if I did another migration I'd spend more time documenting my steps and hopefully get to a functioning local build. If this would be helpful, reply to this message and I'll get back to you with the documentation of my experience in what I think is a typical Dev environment.

[vnbaaij]

Hi,

Yes, input is greatly appreciated. Please share your findings.

[bdelaney]

The attached document provides a complete description of my environment and what I did to create a test project with the v5 RC.
Dev Environment.docx

But I continued....
I thought my errors may be due to old bin/debug files. I deleted the two folders in the project. I rebuilt. Worked. But the Run&Debug did not. Seemed to be a .NET 10 SDK problem. I did my install of that several days ago with Winget. I uninstalled the SDK. Then reinstalled it using the full .exe installer. I restarted my system. I was able to build. Then Run/Debug. Voila. It works. I still have css href problem. Below I show devtool error when app is running in browser.

[vnbaaij]

And your help is definitely appreciated. The reboot.css file is ours,not from Bootstrap.
We are all non-native English people sorry if our language is not always clear or sounds harsh. That is not intentional.

I'll need to give your steps a try to see for myself what is happening. I'll try that in the coming days.

[vnbaaij]

Ok. Was able to get your code and ran it. Issue with the reboot.css file is that it is missing a '/' at the beginning of the import. It should read as:

@import '/_content/Microsoft.FluentUI.AspNetCore.Components/css/reboot.css';

I'm creating a PR to fix this for the next release of the Templates package

With regards to the Counter page and the Badge: The v5 Badge dos not use ChildContent anymore to render the content. Instead it now uses the Content parameter so it should read as:

<p role="status">Current count: <FluentBadge Appearance="BadgeAppearance.Filled" Content="@currentCount.ToString()"></FluentBadge></p>

That change is mentioned at https://fluentui-blazor-v5.azurewebsites.net/Badges/Badge#general so surprised the MCP server did not offer help with that. The wording of the text on the site will be changed a bit in the next doc update

[dvoituron]

Thank you very much, @bdelaney.
I understand your approach better now. I thought you wanted to create a new project, but I didn't realize you were using the FluentUI Blazor v4 template.

The Installation page explains how to create a v5 project from an empty Blazor template... which may be easier for now because, unfortunately, we had to add a lot of breaking changes between v4 and v5.

Otherwise, for migration, it's probably easier to migrate component by component using MCP and the documentation (and being explicit in the migration prompt).

Personally, I would not recommend using Reboot.css v5 anymore, as I don't think it adds anything.

[AClerbois]

Hi @bdelaney,

Thank you for sharing your experience — this kind of feedback is exactly what we need during the RC phase.

To clarify, yes, one of the core purposes of the MCP server is to assist both v4 and v5 users in achieving a smooth migration. In its current state (v5 RC1), the MCP server can retrieve the "how to migrate" documentation for each component individually, which should help guide you through the breaking changes on a per-component basis.

That said, this migration documentation is still evolving and will continue to be refined through the upcoming RC releases to become as accurate and comprehensive as possible.

Your feedback on using the MCP server for migration would be extremely valuable to us. It would help us keep improving the documentation and the tooling — and ultimately extend it from handling small, individual component migrations to supporting larger-scale, more industrialized migration scenarios.

Don't hesitate to share any issues or suggestions you encounter along the way!

[dvoituron]

A last "detail": Adrien worked on a Migration service in this PR #4546.
The RC2 will contains this feature, not yet available.