-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Syntax coloring broken after updating to 17.10 #73862
Comments
I have a demo project in this ticket help to reproduce. I can't give it as public here, refer to the ticket I mentioned to achieve it. |
Here's the demo project and screen shot I attached to my posting on https://developercommunity.visualstudio.com/t/Syntax-coloring-broken-after-updating-to/10675230 |
After visual studio is loads a solution, types declared in other files are not colorized in files that have opened automatically. The workaround is to switch to another file and then back, forcing it to refresh. If the model service cannot access the internet or hangs for some other reason, then almost every type doesn't colorize until you edit the file. There are no workarounds. Reopening the file will break all the colors again. |
@CyrusNajmabadi This looks related to the tagging of full semantics after frozen partial semantics tagging finishes |
Fixed with #72878. |
This issue has been moved from a ticket on Developer Community.
[severity:It's more difficult to complete my work] [regression] [worked-in:17.9]
Syntax coloring doesn't work correctly when loading a project and viewing a file. Issue only started after updating to 17.10.
Broken coloring:
Correct coloring:
Original Comments
Chris Conti on 6/4/2024, 02:02 PM:
(private comment, text removed)
Feedback Bot on 6/4/2024, 08:00 PM:
(private comment, text removed)
Đức Tài Nguyễn on 6/4/2024, 08:31 PM:
(private comment, text removed)
U_1337743 on 6/5/2024, 11:01 AM:
(private comment, text removed)
Feedback Bot on 6/5/2024, 11:02 AM:
(private comment, text removed)
Original Solutions
(no solutions)
The text was updated successfully, but these errors were encountered: