I am using JetBrains Rider 2025.3.2 on macOS with a MudBlazor project targetting .NET 8, C# 12. The project builds and runs correctly, and the same codebase works without any issues in Visual Studio, but Rider does not recognize some MudBlazor components in .razor files.
Common component namespaces imported globally via _Imports.razor using the global:: prefix, for example:
@using global::MyProject.Components.General
In a Razor page, example, Test.razor file, I use components like:
<General Items="@Items" />
At runtime everything works as expected, and the project builds successfully. However, in Rider, the component is marked as unresolved with errors such as “Can’t resolve component ‘General’. Do you want to add the missing namespace import directive?” This issue occurs only in Rider and only in Razor files.
I have verified that the project targets .NET 8 with C# 12, that the global:: prefix is valid and supported, and that _Imports.razor is correctly applied at runtime. The same code works correctly in Visual Studio, and clearing invalidate caches or restarting Rider does not resolve the problem. In Rider 2025.3.x, there also appear to be no available settings to configure Razor or Razor LSP behavior.
Due to project constraints, I cannot remove the global:: prefix from _Imports.razor, and I would prefer not to add duplicate @using directives to every individual .razor page. I am therefore looking for a Rider-side solution or confirmation that this behavior is a known limitation.
Is this a known issue or limitation in JetBrains Rider’s Razor/Blazor IntelliSense when using global:: imports in _Imports.razor? If so, is there a recommended workaround in Rider, or is this something that can only be fixed by JetBrains?
