Skip to content
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

Razor syntax highlighting not occurring for most of my .razor files #8177

Closed
caliberdigitalllc opened this issue Jan 26, 2023 · 4 comments
Closed
Assignees
Labels
✔️ resolution: duplicate This issue or pull request already exists

Comments

@caliberdigitalllc
Copy link

Greetings all. Running 17.5.0 Preview 3, also tried updating to preview 4 this morning. Most of my razor files do not have color coding. IE, in dark mode, all the text is white, in light mode, all the text is black.

  • Doesn't matter if the file has a code behind (file.razor.cs) or not
  • Doesn't affect all files
  • Started out of the blue a week or so ago with no system changes
  • Doesn't seem to affect "newly created" razor components, just existing ones.

Not sure where to start with this one. Screenshot attached.

I have tried resetting all settings to default as well as a full reinstall of VS2022.

This is .net core 7.0.2.

Thanks.

Screenshot_2

@ghost ghost added the untriaged label Jan 26, 2023
@ryanbrandenburg
Copy link
Contributor

This is likely a duplicate of #7966. If you temporarily comment out your ValidationMessage tags do you get coloration back?

@caliberdigitalllc
Copy link
Author

no, but strangely if I comment out all of the DevExpress components, the color comes back. I will try removing and reinstalling their stuff and report back.

@ryanbrandenburg
Copy link
Contributor

It is not an issue with their components (no component should be able to break colorization, it should at worst not be recognized), it's a bug in the tooling which should be fixed by this PR (likely the DevExpress component in question use Generic Type parameters under the covers). We just got that fix into the upcoming preview release, so once that's available updating Visual Studio should resolve the issue.

@ryanbrandenburg ryanbrandenburg added the ✔️ resolution: duplicate This issue or pull request already exists label Jan 26, 2023
@ryanbrandenburg ryanbrandenburg self-assigned this Jan 26, 2023
@ghost ghost removed the untriaged label Jan 26, 2023
@caliberdigitalllc
Copy link
Author

Thank you! Yeah I played with commenting various parts out, and realized it was just really weird patterns that made it work. Thanks for the fix! I'll look very forward to it :D

@ghost ghost locked as resolved and limited conversation to collaborators Feb 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
✔️ resolution: duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants