Skip to content

Upgrade to .NET 10.0 and MudBlazor V9#53

Merged
versile2 merged 22 commits intoMudXtra:devfrom
versile2:update/mudv9net10
Feb 24, 2026
Merged

Upgrade to .NET 10.0 and MudBlazor V9#53
versile2 merged 22 commits intoMudXtra:devfrom
versile2:update/mudv9net10

Conversation

@versile2
Copy link
Collaborator

@versile2 versile2 commented Feb 23, 2026

Updated target frameworks to .NET 10.0 across multiple projects to leverage the latest runtime features. Refactored CardClassname in MudXOutline.razor.cs to use ToDescription() for CSS class generation. Added net10.0 to TargetFrameworks in MudX.csproj.

Closes #52

✨ What’s New or Changed?

📸 Screenshots / Demos (if applicable)

🧪 How Was It Tested?

📂 Type of Change

  • 🐞 Bug fix (non-breaking)
  • ✨ New feature (non-breaking)
  • 💥 Breaking change (will be held until a major release)
  • 📝 Documentation only

✅ Ready for Review

  • PR targets the correct base branch (dev)
  • Code matches MudX style and formatting
  • Any visual changes are clearly shown (screenshots or video)
  • New or updated tests are included where applicable
  • I’ve run and passed local builds/tests

Updated target frameworks to .NET 10.0 across multiple projects to leverage the latest runtime features. Refactored `CardClassname` in `MudXOutline.razor.cs` to use `ToDescription()` for CSS class generation. Added `net10.0` to `TargetFrameworks` in `MudX.csproj`.
Copilot AI review requested due to automatic review settings February 23, 2026 03:06
@gemini-code-assist
Copy link

Summary of Changes

Hello @versile2, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on advancing the project's core dependencies by upgrading several components to target .NET 10.0, ensuring the application can leverage the latest runtime features and improvements. Concurrently, it includes a refactoring within the MudXOutline component to standardize CSS class generation, and streamlines the API documentation for the Blazor.Lottie.Player by removing redundant property descriptions.

Highlights

  • .NET 10.0 Upgrade: Multiple projects, including MudX.Docs.Hybrid.Client, MudX.Docs.Hybrid, MudX.Docs.Server, and MudX.Docs, have been upgraded to target .NET 10.0. The main MudX.csproj now also includes net10.0 in its target frameworks.
  • MudXOutline Refactoring: The CardClassname property in MudXOutline.razor.cs was refactored to use Color.ToDescription() instead of Color.ToDescriptionString() for generating CSS classes, aligning with updated practices or API changes.
  • Blazor.Lottie.Player API Documentation Updates: Documentation for Blazor.Lottie.Player has been updated. Specifically, the TotalAnimationFrames property in LottiePlayer and CurrentFrame, TotalFrames properties in LottiePlayerModule had their descriptions removed or set to null in both XML and JSON API definition files.
Changelog
  • src/MudX.Docs.Hybrid/MudX.Docs.Hybrid.Client/MudX.Docs.Hybrid.Client.csproj
    • Updated the target framework from net9.0 to net10.0.
  • src/MudX.Docs.Hybrid/MudX.Docs.Hybrid/MudX.Docs.Hybrid.csproj
    • Updated the target framework from net9.0 to net10.0.
  • src/MudX.Docs.Server/MudX.Docs.Server.csproj
    • Updated the target framework from net9.0 to net10.0.
  • src/MudX.Docs/MudX.Docs.csproj
    • Updated the target framework from net9.0 to net10.0.
  • src/MudX.Docs/wwwroot/api/Blazor.Lottie.Player.xml
    • Removed XML documentation for the TotalAnimationFrames property.
    • Removed XML documentation for CurrentFrame and TotalFrames properties from LottiePlayerModule.
  • src/MudX.Docs/wwwroot/api/LottiePlayer.api.json
    • Set the description for TotalAnimationFrames to null.
    • Updated the default ElementId value.
  • src/MudX.Docs/wwwroot/api/LottiePlayerModule.api.json
    • Set the description for CurrentFrame to null.
    • Set the description for TotalFrames to null.
  • src/MudX/Components/MudXOutline/MudXOutline.razor.cs
    • Changed ToDescriptionString() to ToDescription() in CardClassname property.
  • src/MudX/MudX.csproj
    • Added net10.0 to the list of target frameworks.
Activity
  • No activity has been recorded on this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request upgrades the project to .NET 10.0 and MudBlazor V9. While the overall transition is clear, there are several hardcoded paths in the project files that still reference .NET 9.0, which will break build cleanup targets. Additionally, there is a documentation regression where several public properties in the Lottie player components have lost their XML documentation, resulting in null descriptions in the generated API metadata. Finally, the refactoring to use a custom ToDescription extension for MudBlazor colors may lead to incorrect CSS class names.

I am having trouble creating individual review comments. Click here to see my feedback.

src/MudX.Docs.Server/MudX.Docs.Server.csproj (4)

medium

The project has been upgraded to net10.0, but the CleanLockedFiles target (line 14) still contains a hardcoded path to net9.0. This will prevent the target from correctly cleaning up artifacts for the new target framework. Consider using $(TargetFramework) to make this path dynamic.

src/MudX.Docs/MudX.Docs.csproj (4)

medium

Similar to the server project, the CleanLockedFiles target (line 22) still references net9.0. This should be updated to net10.0 or changed to use the $(TargetFramework) property for better maintainability.

src/MudX.Docs/wwwroot/api/Blazor.Lottie.Player.xml (225-229)

medium

The documentation for TotalAnimationFrames has been removed. This causes the API generator to produce a null description in the corresponding JSON metadata. If this property is still part of the public API, its documentation should be preserved.

src/MudX.Docs/wwwroot/api/Blazor.Lottie.Player.xml (335-344)

medium

The documentation for CurrentFrame and TotalFrames has been removed from the XML file. This results in a regression in the API documentation where these properties now lack descriptions in the JSON output.

src/MudX/Components/MudXOutline/MudXOutline.razor.cs (80)

medium

The refactoring from ToDescriptionString() to ToDescription() for the Color parameter is a regression in behavior. ToDescriptionString() is a MudBlazor extension that ensures lowercase output and handles specific enum values correctly, whereas the custom ToDescription() extension returns the enum name (e.g., 'Default') if no DescriptionAttribute is present. This results in incorrect CSS class names like 'mud-theme-Default' instead of 'mud-theme-default'.

            .AddClass($"mud-theme-{Color.ToDescriptionString()}")

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR aims to upgrade the MudX project to .NET 10.0 and MudBlazor V9. However, the implementation is incomplete with several critical issues.

Changes:

  • Added net10.0 target framework to multiple projects (.csproj files)
  • Refactored one usage of ToDescriptionString() to ToDescription() in MudXOutline.razor.cs
  • Modified API documentation files (descriptions set to null and auto-generated IDs changed)

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 7 comments.

Show a summary per file
File Description
src/MudX/MudX.csproj Added net10.0 to TargetFrameworks (but MudBlazor version not upgraded)
src/MudX/Components/MudXOutline/MudXOutline.razor.cs Changed ToDescriptionString() to ToDescription() for Color enum
src/MudX.Docs/wwwroot/api/LottiePlayerModule.api.json Property descriptions set to null
src/MudX.Docs/wwwroot/api/LottiePlayer.api.json Property description set to null, auto-generated ElementId changed
src/MudX.Docs/wwwroot/api/Blazor.Lottie.Player.xml XML documentation entries removed
src/MudX.Docs/MudX.Docs.csproj Updated TargetFramework to net10.0
src/MudX.Docs.Server/MudX.Docs.Server.csproj Updated TargetFramework to net10.0
src/MudX.Docs.Hybrid/MudX.Docs.Hybrid/MudX.Docs.Hybrid.csproj Updated TargetFramework to net10.0
src/MudX.Docs.Hybrid/MudX.Docs.Hybrid.Client/MudX.Docs.Hybrid.Client.csproj Updated TargetFramework to net10.0

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 25 out of 25 changed files in this pull request and generated 1 comment.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@versile2 versile2 merged commit c47192c into MudXtra:dev Feb 24, 2026
2 checks passed
@versile2 versile2 deleted the update/mudv9net10 branch February 24, 2026 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MudX alignment to MudBlazor 9.0.0?

2 participants