I love it when I have some spare time to work on something interesting.

What you see in the image is the full UI representation of X/Twitter UI, done 100% in Blazorise. Ain't that interesting??

What is your opinion on line ending in C#, razor, files? And especially for EOF empty line. Personally I hate it. But want to know what is other people opinion...

Announcing Blazorise 2.1 - Mosor Blazorise 2.1, codenamed Mosor after the majestic mountain range in Croatia, is a significant update that brings a host of new features, enhancements, and optimizations to the framework. This release…

Blazorise 2.1 is now available.

One of the largest releases so far, introducing Material 3, AntDesign provider, DataGrid hierarchical data support, and a new Maps extension.

Many components have been improved, including accessibility and responsiveness.

blazorise.com/news/release...

Blazorise 2.1 is coming tomorrow, but we're already working on the future versions.

👀

Check out our Blazorise Outlook Clone developed entirely with Blazor.

This open-source project showcases everything you can do using Blazorise components and theming to build a professional email client UI.

Find all the details here: github.com/Megabit/Blaz...

Blazorise 2.0.4 - Usability and Stability Improvements Blazorise 2.0.4 brings improvements to DataGrid keyboard navigation, fixes Select value handling, and resolves multiple issues across components and providers.

🚀 Blazorise 2.0.4 released

• Better DataGrid keyboard navigation (arrow keys)
• Fix for Select<TValue> with nullable values
• Multiple fixes across Autocomplete, DatePicker, charts & providers

Release notes:
blazorise.com/news/release...

#blazor #dotnet

Almost done... 👀

Blazorise 2.0.3 - Introducing the New Gantt Component Blazorise 2.0.3 introduces a powerful new Gantt component along with improvements to DataGrid filtering and MemoInput behavior.

🚀 Blazorise 2.0.3 released

New ✨ Gantt component
• Editing, drag & drop, hierarchy
• Built via Custom Work → now available to all

Fixes for DataGrid filtering & MemoInput in modals

Release notes:
blazorise.com/news/release...

#blazor #dotnet

Gantt component by stsrki · Pull Request #6454 · Megabit/Blazorise This PR introduces a new Gantt component for Blazorise. It adds a hierarchical tree-and-timeline task view with declarative columns and views, built-in editing, drag interactions, sorting, keyboard...

Something new is coming to Blazorise 🤯

github.com/Megabit/Blaz...

Blazorise 2.0.2 - Accessibility and Stability Improvements Blazorise 2.0.2 focuses on critical stability fixes, improved accessibility, better keyboard navigation, and several DataGrid and Tailwind theming corrections.

🚀 Blazorise 2.0.2 released

Fixes include:

• Critical InsufficientExecutionStackException (#6427)
• Better keyboard navigation in dropdowns
• Accessibility improvements for menu components
• DataGrid, FilePicker & Tailwind fixes

Release notes:
blazorise.com/news/release...

#blazor #dotnet

The first preview of Material 3 for Blazorise is live.

Built completely from scratch by our team, with fully reworked components and theming aligned with Material 3.

Preview the demo: preview-demos.blazorise.com/wasm/material/

Feedback is welcome.

#Blazor #DotNet #Material3 #Blazorise

Who is interested in trying out our brand-new Material 3 for Blazorise?

Blazorise 2.0.1 - First Stability Update for 2.0 Blazorise 2.0.1 delivers important fixes across NumericPicker, DatePicker, DataGrid, Collapse, and Charts, refining the 2.0 experience based on early production feedback.

Blazorise 2.0.1 is live 🚀

Stability update for 2.0:

✔ NumericPicker value sync
✔ DatePicker indicator fix
✔ DataGrid DetailRow fix
✔ Collapse fix
✔ Chart responsiveness

No breaking changes. Safe update.

blazorise.com/news/release...

And I go back and reiterate or change direction. So basically, nothing changed in how I work; I'm just faster than before because I don't need to do many manual, tedious tasks.

The sweet spot I found when working with AI agents is not to one-shot it all at once. Instead, I approach it like I always worked. Work in iterations. Do one small thing, then the next thing. And so on. Then, after a while, I notice something is wrong.

Support Event Modifiers (stopPropagation, preventDefault) for Component Event Parameters · Issue #65459 · dotnet/aspnetcore Is there an existing issue for this? I have searched the existing issues Is your feature request related to a problem? Please describe the problem. In Blazor, event modifiers such as @onclick:stopP...

Let us see how it goes... github.com/dotnet/aspne...

If you're annoyed like I am with the too-large spacing of items in the Solution Explorer of the latest VS26, here is the option to fix it.

You're welcome!

Blazorise ROI Calculator Estimate in-house UI build costs, total cost of ownership, and Blazorise licensing to compare build-vs-buy ROI, projected savings, and time-to-market impact.

As the founder of Blazorise, I know what it really takes to build a UI library.

So we built an ROI calculator to help teams compare build vs buy realistically: blazorise.com/roi-calculator

#Blazor #DotNet #Blazorise

Haha, no worries. Thank you!

Announcing Blazorise 2.0 - Velebit Blazorise 2.0, codenamed Velebit after the majestic mountain range in Croatia, is a significant update that brings a host of new features, enhancements, and optimizations to the framework. This…

If you’ve used Blazorise over the years, thank you.

If you’re new, 2.0 is the strongest starting point yet.

Full release notes 👇
blazorise.com/news/release...

#blazor #dotnet

Some breaking changes were necessary.

But they were intentional, to remove legacy friction and build a stronger base for the next phase of Blazorise.

2.0 isn’t about flashy features.

It’s about foundations:

✔ Unified input API
✔ Cleaner validation system
✔ Modernized providers
✔ Migration CLI + Analyzer

Consistency > convenience.

Version 2.0 represents nearly 3 years of focused work.

Since 1.0:
• 8 major releases
• Dozens of minor releases
• Thousands of bug fixes
• Continuous improvements

Longevity matters.

Blazorise started in 2018.

Almost 8 years later, we’ve just released Blazorise 2.0 🏔️

This one feels different.

🧵👇

Blazorise - Blazor Component Library Ship accessible, production-ready Blazor apps quickly with 80+ components, consistent theming, and first-class support for Bootstrap, Tailwind, Bulma, AntDesign, and Material.

Have you had a chance to test Blazorise 2.0 preview? We're launching the final version in just two days, so any bug reports would greatly help us refine it.

preview.blazorise.com

#Blazorise #TechFeedback

Blazorise 1.8.10 - Table Scrolling & Globalization Improvements Blazorise 1.8.10 delivers a fix for Table ScrollToRow visibility, adds support for Invariant Globalization, and resolves Signature Pad input issues on iOS Safari.

Blazorise 1.8.10 is out 🚀

Small release, real impact:

• Table ScrollToRow visibility fixed
• Invariant Globalization support
• Signature Pad works again on iOS Safari

All safe, drop-in fixes for 1.8.x 👇
blazorise.com/news/release...

Building a Design System on Top of Blazorise How to layer Blazorise into a product-grade design system with abstracted components, opinionated wrappers, and sustainable versioning and docs.

Building a design system on top of Blazorise isn't about more components; it's about deciding what teams shouldn't have to think about anymore.

Some notes on layering, opinionated wrappers, and keeping things flexible.

👉 blazorise.com/blog/buildin...

Weekend project 👀

I spun up an MCP server for Blazorise so AI tools can query real docs & examples instead of relying on training data.

Early preview:

mcp.blazorise.com/mcp/sse

Responsive layouts in Blazor != media queries everywhere.

We wrote a deep dive on:

• Grid vs Flex (when to use each)
• Mobile-first layouts with breakpoints
• Why Blazorise utilities > inline styles

👉 blazorise.com/blog/respons...

Opt-in extensibility for Blazor parameter change detection · Issue #65135 · dotnet/aspnetcore Is there an existing issue for this? I have searched the existing issues Is your feature request related to a problem? Please describe the problem. Blazor currently uses a conservative change-detec...

Opened a new Blazor feature request today 🚀

Proposal: an opt-in IChangeDetection extensibility point so advanced apps can customize parameter equality (e.g., value objects/records), without changing default Blazor behavior.

Hoping for a good discussion

github.com/dotnet/aspne...