Open garrettlondon1 opened 1 year ago
Thanks for the report. This is the same underlying problem that causes https://github.com/dotnet/razor/issues/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
Firm is a class, Modal is a component reference, and syntax highlighting is lost with Omnisharp disabled. I even tried restarting the language server, and sorry to jump off topic, but that's why I can't disable Omnisharp. Shoutout dan roth for the searchbox component :)
Here is the same with Omnisharp enabled 5 mins later after files were indexed
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 razorbgvirtual.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