| T O P I C R E V I E W |
| BeigeAlert |
Posted - Oct 17 2019 : 2:26:49 PM
Is anybody else having issues with VS2019 and VA? Previous versions have worked flawlessly, but it seems lately, either a VA update or updating to VS2019 is causing a lot of odd issues.
Chief among them:
- The VA context menu will eventually stop working and requires a restart of VS (eg shift+right click brings up the VS menu, not the VA menu). I have tried disabling the option and re-enabling it, but it seems the only solution is to restart VS.
- Sometimes, typing a . in another tab has no effect, and instead adds a period where the cursor is in a completely different tab (within the same tab-group though).
Unfortunately I don't have any repro for these issues as they're all intermittent, but I'll update here if I encounter other bugs/find better repro other than "eventually it happens". |
| 22 L A T E S T R E P L I E S (Newest First) |
| sean |
Posted - Nov 14 2019 : 2:18:46 PM
Good to hear, thanks for the update. |
| freeman40 |
Posted - Nov 14 2019 : 03:49:36 AM
Thanks for your hard work on this. I've been using 2353 with VS2019 (and with the preview tab re-enabled) for a couple of days now, and no issues so far :-) |
| sean |
Posted - Nov 07 2019 : 7:17:25 PM
case=137431 is fixed in build 2353
https://support.wholetomato.com/default.asp?W404#2353
|
| phillipfoose |
Posted - Nov 07 2019 : 3:17:24 PM
It's worth noting, that when updating visual studio (at least these minor 16.3.x point releases) the preview option is getting turned on after each update, so worth checking after an upgrade of VS itself. |
| sean |
Posted - Nov 01 2019 : 11:52:05 AM
@Foddex I have sent direct mail to you regarding your experience. |
| Marc aka Foddex |
Posted - Nov 01 2019 : 03:26:13 AM
quote:
Originally posted by BeigeAlert
Is anybody else having issues with VS2019 and VA? Previous versions have worked flawlessly, but it seems lately, either a VA update or updating to VS2019 is causing a lot of odd issues.
Chief among them:
- The VA context menu will eventually stop working and requires a restart of VS (eg shift+right click brings up the VS menu, not the VA menu). I have tried disabling the option and re-enabling it, but it seems the only solution is to restart VS.
- Sometimes, typing a . in another tab has no effect, and instead adds a period where the cursor is in a completely different tab (within the same tab-group though).
Unfortunately I don't have any repro for these issues as they're all intermittent, but I'll update here if I encounter other bugs/find better repro other than "eventually it happens".
I have these issues as well, plus general instability and regular crashes when VA 2341.2 is enabled (say 10-20x in a 8 hour workday...). Without VA VS is 100% stable for me.
Can't wait for that next build, as I really miss my VA features!
|
| sean |
Posted - Oct 31 2019 : 8:26:41 PM
We have the fix in an internal build. It is still being tested. A public release should be available within a week. |
| Waves |
Posted - Oct 31 2019 : 7:01:37 PM
I also have these issues. VA will randomly stop working and the only way to fix it is to restart Visual Studio.
In addition sometimes typing . or ( will cause Visual studio to redirect keyboard input to a different tab at it's last cursor location. Effectively ruining that file. This is terrible, I was about to uninstall VA but disabling the preview tab like stated above has fixed these issues.
However I need the preview window. It makes things difficult when working with a large codebase like Unreal to not have a preview option. I hope this gets fixed soon. |
| feline |
Posted - Oct 30 2019 : 07:58:05 AM
Thank you for the update, we are hoping for a fix in VA soon, but it is good to know that you are able to work safely and reliably for now. |
| DDS-Trond |
Posted - Oct 30 2019 : 07:32:21 AM
I can confirm that after I re-enabled VA and disabled preview tab a week ago, there have been no issues. I will keep the preview tab disabled until this is fixed. |
| sean |
Posted - Oct 22 2019 : 4:27:42 PM
Thanks for the info everybody. We have been able to repro with 2333, so it definitely seems to be caused by a recent VS update. We hope to have a workaround in the next release -- which is now delayed for this and one other issue. |
| phillipfoose |
Posted - Oct 22 2019 : 2:08:25 PM
Me and multiple co-workers were experiencing exactly this. We've just now switched off the preview window and so far so good. Only started happening in the last week or two, seemed to coincide with a Visual Studio update (i'm now on 16.3.5), as I hadn't updated VA in a while.
VA_X.dll file version 10.9.2341.2 built 2019.08.05
DevEnv.exe version 16.3.29411.108 Professional
msenv.dll version 16.0.29318.209
Comctl32.dll version 6.10.18362.418
Windows 10 10.0 1903 Build 18362.418
12 processors (x86-64, WOW64)
Language info: 1252, 0x409
Platform: Project defined
Stable Includes:
C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\Include\um;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\cppwinrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\winrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\ucrt;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\VS\include;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.23.28105\atlmfc\include;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.23.28105\include;
Other Includes:
Stable Source Directories:
C:\Program Files (x86)\Windows Kits\10\Source\10.0.18362.0\ucrt;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\VS\src;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.23.28105\crt\src;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.23.28105\atlmfc\src\atl;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.23.28105\atlmfc\src\mfcm;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.23.28105\atlmfc\src\mfc; |
| freeman40 |
Posted - Oct 21 2019 : 4:42:00 PM
Thanks for those suggestions. I will try them and let you know how it goes.
UPDATE: Today I have used the 2333 build without any issues (I still have the "preview tab" enabled).
Tomorrow I will try again with 2341.2 (with preview tab enabled) to see if problems return, and then try it with preview tab disabled.
|
| sean |
Posted - Oct 21 2019 : 2:46:43 PM
Disabling the Preview Tab appears to prevent the problem. Does unchecking the following setting prevent the problem for any of you?
Tools | Options | Environment | Tabs and Windows | Preview Tab | Allow new files to be opened in the preview tab |
| accord |
Posted - Oct 21 2019 : 09:07:45 AM
Instead of disabling VA, could you guys please install a previous version of Visual Assist, say Build 2333, to see if it makes any difference?
It could help you working and also, if it's a regression, it's usually useful for us to know which build did the regression happen. (we can reduce the possible causes to a number of changelists)
We'll continue looking into the issues. |
| Grabovsky |
Posted - Oct 21 2019 : 04:13:29 AM
I have same issues. But second one appears when I try to type round braces. |
| DDS-Trond |
Posted - Oct 21 2019 : 02:50:20 AM
I have also unfortunately had to disable VA. In it's current unstable state, it is costing more time than it saves. |
| freeman40 |
Posted - Oct 20 2019 : 4:33:59 PM
I am encountering the first bug constantly. The visual assist context menu stops working (and also VA keyboard shortcuts stop working). After restarting Visual Studio, VA works for an hour or two, and then stops working again.
I am also experiencing strange behaviour when typing a dot in a code editor window. Sometimes it works, and sometimes instead of a adding a dot to my code, a random menu pops open on some other part of the screen.
Its frustrating. VA is unusable in this state, and I have disabled it.
Coding in C++. Using VS 2019 16.3.5, on windows 10 1903.
|
| BeigeAlert |
Posted - Oct 17 2019 : 10:58:06 PM
I'm using version 16.3.5.
Good to know about the workaround.
As for the second issue, it hit me constantly one day, but much less recently, very bizarre. I've since just gone back to using VS2017 for the time being (projects target 2017 anyways, so it's not too much trouble). |
| sean |
Posted - Oct 17 2019 : 6:14:46 PM
We now have steps to repro the missing nav bar problem (which also manifests in VA commands not being available, etc). It appears to be due to a change in one of the recent 16.3 updates and also affects 16.4 preview. We are still investigating.
When it occurs, the workaround is to close any editor for which the VA Nav Bar does not appear (after the editor gets focus), and then use alt+left to reopen it. |
| DDS-Trond |
Posted - Oct 17 2019 : 2:56:34 PM
At my company, we have encountered the second of those issues on at least three different computers. We run the latest versions of Visual Studio 2019.
It happens several times every day, one of my coworkers have uninstalled Visual Assist because of it. I really hope it will be fixed soon, otherwise I'm afraid we can't use it any more until it gets fixed.
When it happens, we have found two ways to make it stop: Restart VS or close the file that the . gets written to. But this is very annoying if we are also working with that file. |
| ChrisG |
Posted - Oct 17 2019 : 2:34:31 PM
For the first issue, we are aware of something similar and are investigating (case 141374). How often does this happen to you? Does closing all tabs and then opening a new tab help?
For the second issue, I don't think we have a report of anything similar. How often does this happen for you?
What version of Visual Studio 2019 are you using? |
