Closed artyomszasa closed 1 week ago
We're sorry you are running into this. We believe we have a fix in progress that should help with this issue; you can follow the status of https://github.com/dotnet/razor/issues/10547 and we will update it when we have a version number that we expect the fix to be in.
I believe this is fixed in v2.39.28 (pre-release)
. Please let me know if you're still having this issue
Blazor/razor broken when using C# extension with version above v2.30.28 . It may be related to razor/blazor yet reverting C# extension to the version specified above workarounds the issue hence reporting the issue here. C# Dev Kit is also installed yet trying different versions yields the same result. Only downgrading C# extension itself helps.
Environment data
dontet --info:
VS Code version: 1.89.1 C# Extension version: v2.34.12 C# Dev Kit version: v1.8.8 (pre-release)
logs
See attachments: csharp.log razor.log
Steps to reproduce
dotnet new blazorwasm
App.razor
Expected behavior
Razor components (both from packages and created in the project) recognized as components.
Actual behavior
Every component is reported as unrecognized (RZ10012)