GoNetWasm VS ant-design-blazor

I've been using AntDesign Blazor with AI-assisted programming for efficient full-stack development. However, I occasionally encountered issues with outdated property usage. Yesterday, an inspiration struck: I could create a CLI tool using .NET to query the JSON artifacts generated during our documentation build, and then add an MCP service for AI editors to call. Taking AntDesign.Cli as an example, this tool queries the latest API information for Ant Design Blazor components, effectively solving the problem of outdated model training datasets.

AntBlazor has a pretty comprehensive set of components, and fairly active.

AntBlazor is the best for me. You can try.

Personally I prefer AntBlazor. AntBlazor

I did some charting work for an internal Blazor tool. I ended up using AntBlazor. I did have to go around their Blazor tool and use the JS project as I had to use it in a certain way. If you're confused on how a component is made - I just looked at their github repo and learned! Sometimes they'll base class a lot of things but it was in some cases easy enough to use and replicate.

I see that page points me to the default.less for Ant Design. I assume the analogous file for AntBlazor is this default.less file.

I recommend Mud blazor if you're going for Material design. For other design languages Andt Blazor's pretty polished and there's Blazorise as well if you want to be flexible (it supports Antd, Bulma, Bootstrap and Material via configuration).

Since everyone is advertising their preferred component library, I will chime in and say a few good words about AntBlazor. I think this is the fastest developing component library, especially when you compare how alive the development is compared to other open source libraries. Also, it has a ready made Pro template. I think it is one of the most feature rich component library. Go check it out :).