| T O P I C R E V I E W |
| jmoleary |
Posted - Feb 13 2024 : 2:24:53 PM
I use VS Coloring in both C++ and C# files.
Earlier today it was working fine in 17.8.6. The I updated Visual Studio to 17.9.0. Now the coloring still works in C++ but it no longer has any effect on C# files. I can enable/disable Visual Assist but nothing changes.
I did not make any other changes. I just updated Visual studio.
Edited to add. I was using a slightly-out-of-date version of Visual Assist. So I updated to the very latest 2024.1 build and the problem persists. |
| 12 L A T E S T R E P L I E S (Newest First) |
| db123 |
Posted - Mar 26 2024 : 05:55:14 AM
Looks like I have to wait for the next version |
| feline |
Posted - Mar 25 2024 : 11:02:22 AM
Odd about your missing post, I don't know what happened there.
VA 2515 has a fix for the missing C# colouring in the editor window, but unfortunately it didn't fix the map mode scroll bar colouring, which was a surprise. |
| Woody |
Posted - Mar 25 2024 : 09:34:16 AM
I don't know why my last post is missing, but I installed the latest VA update 2515 and the enhanced syntax coloring is working for me again (VS 17.9.4) |
| feline |
Posted - Mar 25 2024 : 09:18:05 AM
I had expected this to be fixed by fixing C# syntax highlighting not working, but apparently map mode scroll bar will require a separate fix. I have put in a bug report for this, since it is still broken in VA 2515
case=164360
Unfortunately no updates, since the bug report has only just gone in. |
| Woody |
Posted - Mar 22 2024 : 10:36:35 AM
Any news on this? I was reporting to MS why I'm reverting to older VS 17.8.7 and they investigated and concluded it's your fault. It's hard to say how deep the investigation was though 
Anyway, it should be fairly easy to investigate if it's 100% repro on any C# code. Do you have at least an estimate when it's going to be fixed? |
| feline |
Posted - Feb 28 2024 : 09:20:02 AM
I don't use the map mode personally, so I hadn't noticed, but yes, turning it on, I am seeing the same problem here. I am guessing that the IDE is just pulling in the editor colouring for this map mode, but that is purely a guess on my part.
Either way, I have made a note on the case about this, so thank you for reporting it. |
| MikMik |
Posted - Feb 28 2024 : 03:58:06 AM
Maybe you can do something in the Visual Assist side to fix it, but I think that Visual Studio has broken the coloring in C#. The map mode in the scroll bars has lost all coloring too... |
| feline |
Posted - Feb 22 2024 : 09:16:51 AM
I have confirmed this with several versions of VA, and across a couple of different preview versions of VS2022 as well, so I am fairly sure this is due to a change in Visual Studio. No updates on this yet, but this is down as a high priority bug, and I suspect we need a change in VA to handle the change in Visual Studio. |
| kornman00 |
Posted - Feb 21 2024 : 5:13:35 PM
Any updates for this bug :)? Is it something we'll need to wait for Visual Studio to fix, or was there a breaking change in the plugin infrastructure that VAX has to cover? FWIW, it occurs in the latest VS2022 Preview as well (17.10). |
| feline |
Posted - Feb 20 2024 : 07:02:29 AM
That is an option, it is good the Visual Studio installer now offers this.
I forgot the case number:
case=164173 |
| Woody |
Posted - Feb 19 2024 : 3:15:30 PM
I have the same issue, but luckily, we can now (since VS 17.4) rollback to previous VS version. No need for full reinstallation.
In the Visual Studio Installer click on "More" button and select rollback. In my case it brought version 17.8.6. The VS installation looked clean though. I was asked to login to my VS account and it was restoring all my settings. I realized that VA is missing, so I installed it again, but all my settings was restored there too. Syntax coloring is working for me again |
| feline |
Posted - Feb 14 2024 : 08:03:06 AM
I am seeing the same thing here, having installed this VS2022 update. I have checked 2 different machines, just in case.
It looks like something has changed inside Visual Studio, causing this problem.
I have put in a high priority bug report for this. Thank you for letting us know about it. |
