Radzen Blazor for Visual Studio Issues

Radzen Blazor Studio
1

Recently purchased a Radzen Teams licence, but have disabled the “Radzen Blazor for Visual Studio (1.38.0)” extension due to issues we are experiencing in Visual Studio 2026 Version 18.5.0 running on Windows 11 Enterprise:-

IntelliSense issues causing: -

  • Incorrect or broken code syntax colour formatting.
  • Predictive auto‑complete does not function correctly; pressing TAB does not accept suggested code.
  • Dragging components from Solution Explorer onto a Razor component file frequently fails or placed incorrectly.

Internal Visual Studio feature errors: -

  • Feature [SemanticTokensFeature] is currently unavailable due to an internal error (stack trace displayed)
  • Feature [DataTipRangeFeature] is currently unavailable due to an internal error (stack trace displayed)
  • Feature [CodeActionFeature] is currently unavailable due to an internal error (stack trace displayed)

Any help on resolving the issues above would be much appreciated!

2

Hi @scottmcintosh,

We would gladly investigate the reported issues but would need assistance from you in order to reproduce them. Can you provide more details? Does any of the issues happen always? Does any of the issue happen in a new app? Any steps to reproduce the issues? Feel free to reply here or send us an email with additional details to info@radzen.com

By the way the Internal Visual Studio error features have been discussed in other threads - they don't seem related to the Radzen Visual Studio plugin as other users have reported them to Microsoft on github. We have not found a clear evidence our plugin is causing them and neither could we reproduce them in local test. Of course if proven wrong we would provide a fix.

3

The issue occurs only when the “Radzen Blazor for Visual Studio (1.38.0)” extension is enabled. Errors appear while editing Razor components and appear to be linked to underlying IntelliSense synchronisation issues. I have reproduced the same behaviour on both my home and my work computer.

4

Can you tell us how to reproduce them at our side? What steps should we follow? I believe most of those issues are caused by the same thing. We just need to reproduce it. For example when does the SemanticTokensFeature appear? Does it happen immediately after opening a .razor file? Does it happen after some time? Does it happen after dragging and dropping a component? Does it happen after using the property grid?

When SemanticTokensFeature happens do you see any errors in the Razor LSP output pane in Visual Studio?

UPDATE: I think I reproduced the issue and we are running an investigation to see how to mitigate it.

UPDATE2: We still haven't found the actual cause and reproduction is sporadic. Can you send us the ActivityLog.xml (%AppData%\Microsoft\VisualStudio\{version}\ActivityLog.xml) file of your Visual Studio @scottmcintosh ? It would have stacktraces that could help.

5

Just released a new version of the extension which should hopefully address the intelissense and syntax highlight issues.