You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Welcome to the MudBlazor Migration Guide for upgrading your project to newer versions. This guide provides essential information to help you transition smoothly to the latest version of MudBlazor.
3
+
4
+
Each release might include new features, improvements, bug fixes, and, in some cases, breaking changes. To ensure you can adopt the new version without issues, we have outlined the necessary steps and linked to detailed migration instructions for specific releases.
5
+
6
+
#
7
+
8
+
### How to Use This Guide
9
+
- Identify Your Current Version
10
+
* Before starting, confirm which version you are upgrading from.
11
+
- Follow the Version-Specific Guide
12
+
* Each release has a dedicated GitHub issue containing all the details for migrating.
13
+
* If you're upgrading across multiple versions, follow each guide sequentially, starting from your current version and progressing to the latest.
14
+
- Address Breaking Changes
15
+
* Pay attention to any breaking changes or deprecated features listed for the target version.
[](https://github.com/mudblazor/mudblazor)
@@ -25,7 +26,7 @@ MudBlazor is an ambitious Material Design component framework for Blazor with an
25
26
-[MudBlazor.com](https://mudblazor.com)
26
27
-[Try.MudBlazor.com](https://try.mudblazor.com/)
27
28
28
-
###Why is MudBlazor so successful?
29
+
## Why is MudBlazor so successful?
29
30
- Clean and aesthetic graphic design based on Material Design.
30
31
- Clear and easy to understand structure.
31
32
- Good documentation with many examples and source snippets.
@@ -40,14 +41,17 @@ MudBlazor is an ambitious Material Design component framework for Blazor with an
:information_source: Currently only interactive rendering modes are supported - [Learn more](https://learn.microsoft.com/aspnet/core/blazor/components/render-modes).
48
+
> [!TIP]
49
+
> If you're updating to a newer version of MudBlazor, make sure to check out the [Migration Guide](https://github.com/MudBlazor/MudBlazor/blob/dev/MIGRATION.md) for detailed instructions on handling breaking changes and new features.
47
50
48
-
:warning: Blazor only supports [current browser versions](https://learn.microsoft.com/aspnet/core/blazor/supported-platforms).
49
-
To ensure a seamless experience with MudBlazor, please use an up-to-date web browser.
50
-
If a browser version is no longer maintained by its publisher, we cannot guarantee compatibility with MudBlazor.
51
+
> [!WARNING]
52
+
> 1. Static rendering is not supported - [Learn more](https://learn.microsoft.com/aspnet/core/blazor/components/render-modes).
53
+
> 2. We cannot guarantee compatibility with browsers no longer maintained by their publishers.
54
+
For the best experience, use an up-to-date browser - See [Blazor supported platforms](https://learn.microsoft.com/aspnet/core/blazor/supported-platforms).
MudBlazor is growing, with a significant reduction in the number of bugs.
4
-
We remain committed to maintaining and improving the project, but as a non-commercial project we rely heavily on community contributions.
5
-
We try to review and merge important bug fixes as soon as possible, so if your bug-fix pull request (PR) is overlooked, please tag a team member.
3
+
MudBlazor continues to thrive with millions of downloads on [NuGet](https://www.nuget.org/packages/MudBlazor/) and thousands of members on [Discord](https://discord.gg/mudblazor).
6
4
7
-
## .NET Versions
5
+
With the recent release of v7, and now v8, we've made significant progress in ensuring the library remains healthy and robust.
6
+
Not only have we introduced countless new features and bug fixes, but we've built a more stable foundation for future development, allowing us to continue moving the project forward to meet the needs of the community.
8
7
9
-
We fully support both .NET 7 and .NET 8, and our top priority is to continue supporting upcoming .NET versions.
8
+
## Migration
10
9
11
-
##Breaking Changes
10
+
### .NET Lifecycle
12
11
13
-
We avoided breaking changes for a very long time and have now finally merged several of them and removed all obsolete APIs from v6 in the move to v7.
14
-
Please view the [v7.0.0 Migration Guide](https://github.com/MudBlazor/MudBlazor/issues/8447) to get an idea of what changes you will have to make in your projects.
12
+
Builds are no longer provided for .NET 6 or .NET 7.
13
+
This change aligns with Microsoft's [.NET support policies](https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core) and lets us focus on providing the best support for newer editions.
15
14
16
-
We may make further breaking changes in the future, but we will try to keep them to a minimum and provide a migration guide for each major release.
15
+
Update your SDK to .NET 8 or .NET 9 to get the latest packages.
17
16
18
-
For those unable to immediately upgrade their projects to v7:
19
-
We will maintain v6.x for some time, largely relying on community contributions for bug fixes and backports.
17
+
### MudBlazor Lifecycle
20
18
21
-
## Looking Ahead
19
+
**v8:**
20
+
This is the current recommended version and all new features and development effort will be directed here.
21
+
22
+
**v7:**
23
+
We will continue to accept bugfixes from the community for v7 but no new features will be introduced and we won't accept any requests.
24
+
25
+
**v6:**
26
+
Support for v6 ended 01/2025 and no new patches will be released.
22
27
23
-
Right now we are focused on getting v7 stable and bug-free.
24
-
After v7 has settled we will start proper work on v8.
25
-
You can find our current plans on the [v8 project board](https://github.com/orgs/MudBlazor/projects/3).
26
-
There is no ETA currently, but we aim to have more regular major releases with less breaking changes in the future.
28
+
### Migrating from a Previous Version
27
29
28
-
Understand that our team members contribute to this project during their personal free time, so please don't expect the team to fix bugs for you.
29
-
It's not feasible for us to offer free support to everyone, but we do our best to review and merge your PRs.
30
-
That being said, we feel responsible for MudBlazor and intend to keep it going for the foreseeable future at a sustainable cost of free time by merging important bug fixes and new features if they enhance the project.
30
+
The release of v7 addressed several long-standing needs for breaking changes and our goal for v8 is to build on that success while ensuring a smoother transition.
31
31
32
-
Please keep giving us your ideas so we can consider them for upcoming versions!
32
+
For help with migrating to a new version, please refer to the [v7.0.0 Migration Guide](https://github.com/MudBlazor/MudBlazor/issues/8447) or [v8.0.0 Migration Guide](https://github.com/MudBlazor/MudBlazor/issues/9953).
33
+
In addition we've created a [built-in analyzer](https://mudblazor.com/features/analyzers) that identifies parameters that have been removed or renamed.
34
+
35
+
## Looking Ahead
36
+
37
+
We are passionate about improving the library but can't make firm promises about release timelines or specific features as the MudBlazor team is made up of volunteers who contribute to the project in their personal time.
38
+
39
+
Our goal is to keep MudBlazor stable, performant, and evolving with thoughtful enhancements, but the pace of development depends on the availability of contributors.
40
+
We appreciate your support as we continue to work on keeping MudBlazor the premiere UI library for Blazor.
33
41
34
42
## Get Involved
35
43
36
-
Contributions from the community are what makes MudBlazor successful. If you are proficient in technologies such as C#, Blazor, JavaScript, or CSS, and you wish to give something back, please contact the team [on Discord](https://discord.gg/mudblazor)! You can join our Contribution Team channel and discuss with other team members what you want to do to help and start making a difference on this very roadmap.
44
+
MudBlazor thrives thanks to our amazing community. Whether you specialize in C#, Blazor, JavaScript, CSS, documentation, testing, or design, your help is always welcome.
45
+
46
+
If you’re interested in contributing, please check out [our contribution guidelines](https://github.com/MudBlazor/MudBlazor/blob/dev/CONTRIBUTING.md) to get started.
47
+
48
+
You can also open an issue, start a discussion, or tag a member of the team in relevant GitHub issues to collaborate with us.
0 commit comments