Blazor with Radzen problem

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

[severity:I'm unable to use this version] [regression]
After upgrading to the latest Visual Studio 2026 (March Update), I started a new Blazor project and add the Nuget package for Radzen Blazor Components - running through the Getting Started instructions to have Radzen properly configured, I tried the sample component. Despite having the button nicely displayed, it did not fire the click event. Carry several tests to check it but as I rendered unable to proceed, I'm rolling back.

---

Original Comments

Feedback Bot on 3/13/2026, 03:15 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

[github-actions]

Triage Summary

Area: area-blazor (Issue involves Blazor components, event handling, and interactive functionality with Radzen Blazor Components)

Type: Insufficient information to classify confidently. This could be:

• A bug if there is a genuine regression in Blazor's event handling after the March 2026 VS update
• An external issue if this is specific to Radzen component library compatibility
• A question if this is a render mode configuration issue

Regression Info

• Previously working version: Not specified - only mentions "after upgrading to the latest Visual Studio 2026 (March Update)"
• Broken since: Visual Studio 2026 (March Update) / implied .NET 10 or later
• Behavior change: Button click events in Radzen components stopped firing after the upgrade
• ⚠️ Note: The reporter has marked this as a regression but provides no specific version numbers, sample code, or details about the Radzen component configuration. More information is needed to determine if this is an ASP.NET Core regression or a third-party library compatibility issue.

Potential Duplicates/Related Issues

• Improve the dev experience when a user doesn't apply an interactive render mode to a component that requires interactivity #57009 - Improve dev experience when interactive render mode not applied (similarity: medium) - addresses the common issue where Blazor components render statically and events don't work
• @onpointerenter and @onpointerleave not firing #34288 - Pointer event handling issues (similarity: low) - different event type but similar symptom of events not firing

Notes

Missing critical information:

1. No code sample - cannot reproduce or diagnose without seeing the component implementation
2. No version information - which .NET version, ASP.NET Core version, or Radzen package version?
3. No render mode details - is the component using @rendermode InteractiveServer, InteractiveWebAssembly, or InteractiveAuto?
4. No error messages or console logs - are there any JavaScript errors or warnings?
5. No project template details - Blazor Server, Blazor WebAssembly, or Blazor Web App?

Most likely cause: Based on the description and similar issues, this may be a render mode configuration problem. Blazor components in .NET 8+ require explicit interactive render modes for event handling to work. Radzen components need to be rendered with an interactive mode.

Recommended action: The issue author should be asked to provide:

• Minimal reproducible code sample
• Specific .NET and Radzen package versions
• Render mode configuration (if any)
• Browser console errors
• Whether the same code works in a previous .NET version

Cannot label as area-blazor or set issue type without more information, as this could be a Radzen-specific issue rather than an ASP.NET Core issue. However, if forced to choose, this would be area-blazor given the event handling context.

---

@vsfeedback To help us investigate this issue, please provide:

1. A minimal code sample showing the Radzen button and click handler
2. Your project's .NET version (check .csproj)
3. The Radzen.Blazor package version
4. The render mode configuration for your component or page
5. Any error messages from the browser console (F12 Developer Tools)

Generated by Issue Triage Agent for dotnet/aspnetcore for issue #66842 · ● 407.3K · ◷

[oroztocil]

Thank you for contacting us. Please provide more details, ideally including a reproduction project.

[dotnet-policy-service]

Hi @vsfeedback. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[dotnet-policy-service]

Thank you for filing this issue. In order for us to investigate this issue, please provide a minimal repro project that illustrates the problem without unnecessary code. Please share with us in a public GitHub repo because we cannot open ZIP attachments, and don't include any confidential content.