-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigating to Component within same RCL goes to razor__bg__virtual.cs #9361
Comments
Thanks for the report. This is the same underlying problem that causes #9369 |
@garrettlondon1 just noticed the "_bg" in the filename. This implies you're using OmniSharp, or have the C# extension set to use OmniSharp at least. Is that correct? Does the problem still exist if you turn that off? |
Sorry, forgot to mention that.. I had tried three modes of working with the extensions setup:
Also, I do not have the C# dev kit installed, I was having performance issues on my Surface 4 with memory usage. Let me try that again |
Omnisharp is able to recognize services @injected into the _Imports.razor, and even with C# dev kit I get CS0246 in the code behind file for unrecognized component references, as well as the component tag in the .razor page is unrecognized. Reloading the window, as well as reopening VS code doesn't help |
That's not off topic, thats reporting bugs 😁 (though okay.. separate issues is probably ideal, but we'd rather have the information somewhere than not) |
Navigating to a component in my razor class library with the latest C# extension in VS code (2.4.4), navigates to a razor__bg__virtual.cs class, but when hovered over, it is successfully able to resolve the component reference and namespace
Note: Closing and reopening the component leads to the same result
Reloading window leads to same result. Note: this is a newly added component, in the same working session
The text was updated successfully, but these errors were encountered: