-
Notifications
You must be signed in to change notification settings - Fork 183
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
Blazor components from same namespace not all recognized. #10275
Comments
dotnet --info Expand
|
OmniSharp Logs-------------------------------------------------------------------------------- Razor.VSCode version 7.0.0-preview.24168.4 -------------------------------------------------------------------------------- Razor's log level is currently set to 'Debug' - To change Razor's log level set 'razor.server.trace' and then restart VSCode. - To report issues invoke the 'Report a Razor issue' command via the command palette. -----------------------------------------------------------------------------------------------------------------------------Using dotnet configured on PATH |
Is this a Bug or Feature request?:
Bug
Steps to reproduce:
Open project in VSCode.
Create some components.
Randomly some components will fail to be recognized.
Please note that this happens on both insiders and non-insiders edition of VSCode.
Description of the problem:
Expected behavior:
All components should be found from the same namespace and not be marked as a warning.
Actual behavior:
Components are randomly marked as not recognized from the same namespace as others.
Logs
OmniSharp
------------------- Please fill in this section -------------------------
Due to length I've posted this on another comment.
Razor
Expand
Workspace information
Razor document:
Expand
Projected CSharp document:
Expand
Projected Html document:
Expand
Machine information
VSCode version: 1.89.0-insider
Razor.VSCode version: 2.23.15
dotnet --info
The text was updated successfully, but these errors were encountered: