| T O P I C R E V I E W |
| Uniwares |
Posted - Apr 12 2024 : 09:45:31 AM
VA_X64.dll file version 10.9.2515.0 built 2024.03.14
DevEnv.exe version 17.10.34804.81 Enterprise
Almost impossible now to edit C# files, even shorter ones. Editor keeps delaying every action, typing, scrolling, selecting. All with a delay of 1-2 seconds.
Disabling VA returns editor to normal. |
| 11 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - May 27 2024 : 10:51:36 AM
pstemper thank you for the update. That is curious, and interesting. We did make some fixes a while ago for performance on a high refresh monitor, and after that were not able to reproduce the problem you were seeing. So this suggests that the specific version of VS2022 could be a factor. Certainly not proof, but if that was true, it would certainly complicate matters slightly.
Uniwares, good to know. Things are looking good for me here, but despite my best efforts, I don't do everything VA can do all of the time  |
| Uniwares |
Posted - May 24 2024 : 09:40:48 AM
Currently using the latest VA on 17.10.0 and 17.11.0 preview 1, no troubles so far on two different machines. |
| pstemper |
Posted - May 24 2024 : 08:50:33 AM
I am currently at 17.9.7 with VA 10.9.2520.0.
The problem seems to have resolved itself now. I have NOT seen the performance issues I was seeing (the latest VA made a BIG difference) for at least a week now, and with the same large project.
I am about to go to VS 17.10.0, so we will see if the issue stays away, or comes back.
PStemper |
| feline |
Posted - May 24 2024 : 06:43:22 AM
pstemper is reporting this problem with VS2022 version 17.9.6, and also on a high refresh rate monitor. So unless you have a high refresh monitor this shouldn't effect you.
Currently I am only aware of a single problem with VS 2022 version 17.10, which is that code inspection results are not showing marks on the vertical scroll bar. Certainly no signs of obvious, major problems so far with the latest VS2022 update. You can always revert VS2022 back to the previous version if required, but its not a quick process. |
| chuckie |
Posted - May 24 2024 : 05:17:37 AM
I am reluctant to upgrade VS to 17.10 if there are such issues with VAX. Because I am out of maintenance I will need to purchase upgrade to resolve.
Do we have a time indication for this issue being resolved? |
| pstemper |
Posted - Apr 26 2024 : 1:13:41 PM
I received your message, and I will be happy to help. I will let you know what I find!!
Thanks |
| feline |
Posted - Apr 26 2024 : 1:06:45 PM
I have emailed you pstemper, that is a massive slow down you are seeing!
case=164501 |
| pstemper |
Posted - Apr 26 2024 : 12:02:59 PM
I too am having this issue, but with VS 17.9.6.
The workaround seems to be working, looking forward to a fix.
If you need any additional information in fixing this issue I would be happy to help. I don't mind testing BETA stuff either. ;)
My environment consists of a solution with 9 projects, and way more C# (712) files then I care to count!! Needless to say, without the workaround VS becomes unresponsive for up to 7 seconds every time I type a single character.
Paul |
| feline |
Posted - Apr 15 2024 : 06:39:08 AM
Thank you for the details. This is smaller than I would have hoped, I definitely over achieved with my stress test solution that reproduces the problem. |
| Uniwares |
Posted - Apr 15 2024 : 05:13:21 AM
832/1186 .cs files / total, about 40% of those .cs files are auto-generated EF migrations |
| feline |
Posted - Apr 12 2024 : 2:37:38 PM
Sadly this is a known problem, it first came up a few days ago. It looks like a change in VA 2515 to handle a change in VS2022 version 17.9.0 C# colouring is a factor. For now, the work around is to turn Off:
VA Options -> Coloring and Attributes -> Apply coloring to -> Text Editors
keeping VA colouring active outside of the text editor doesn't seem to matter.
How many C# files do you have in your solution? If you use the VA Open File in Solution dialog, and filter it on .cs the first number on the title bar should be fairly accurate. I am just trying to get a sense of scale, since this problem only seems to happen in "larger" C# solutions, but I don't yet have a good definition of "larger".
case=164409 |
