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
I will write down our plans for Blazorise 2.0 in this ticket.
The general plan is to release 1.7 sometime in October 2024. This version will introduce some new components(like PdfViewer, and Skeleton) and minor API cleanups while making existing APIs obsolete.
After that, we will start working on the next major version, 2.0. With 2.0, we plan to clean major APIs that we believe will improve our users' QoL—starting with #5596. Then all obsolete APIs will be removed.
In parallel with cleaning and improving the component APIs, we also plan to drop support for older .NET versions.
The plan is to remove
NET6
NET7
and keep
NET8
NET9 (once it is released)
Older .NET versions keep us from improving Blazorise in some areas, so this is the perfect time to do it. NET 8 is also marked as LTS, so for the majority of our users, it should be fine. Hopefully.
All these changes will obviously, as usual, be written down in our release notes with all migration steps clearly described.
The text was updated successfully, but these errors were encountered:
I will write down our plans for Blazorise 2.0 in this ticket.
The general plan is to release 1.7 sometime in October 2024. This version will introduce some new components(like PdfViewer, and Skeleton) and minor API cleanups while making existing APIs obsolete.
After that, we will start working on the next major version, 2.0. With 2.0, we plan to clean major APIs that we believe will improve our users' QoL—starting with #5596. Then all obsolete APIs will be removed.
In parallel with cleaning and improving the component APIs, we also plan to drop support for older .NET versions.
The plan is to remove
and keep
Older .NET versions keep us from improving Blazorise in some areas, so this is the perfect time to do it. NET 8 is also marked as LTS, so for the majority of our users, it should be fine. Hopefully.
All these changes will obviously, as usual, be written down in our release notes with all migration steps clearly described.
The text was updated successfully, but these errors were encountered: