| Author |
 Topic  |
|
Kaidoom
New Member
Morocco
3 Posts |
 Posted - Nov 01 2021 : 5:05:27 PM
|
I have this weird issue where the suggestion list appears at the top left when I start typing, this happens 50% of the time when I open a project and doesn't solve itself, If I disable visual assist the normal intellisence suggestion list looks normal but enabling again brings back the issue.
I'm using visual studio 2022 Preview 7
Latest VA update.
Any suggestions ? Thank you.
|
|
|
feline
Whole Tomato Software
United Kingdom
19054 Posts |
Posted - Nov 02 2021 : 07:07:39 AM
|
That is really odd, and my first thought is something to do with your monitor / display settings.
Are you working on more than one monitor?
Have you changed the scaling / DPI setting on the monitor you are seeing this happen on? If so, what have you changed it to?
Do you have a high refresh rate monitor? |
zen is the art of being at one with the two'ness |
 |
|
|
feline
Whole Tomato Software
United Kingdom
19054 Posts |
Posted - Nov 02 2021 : 07:08:49 AM
|
| Another user has reported an odd problem in VS2022 preview, running under a preview version of Windows. Which OS are you using, and is it a preview / insider version, or a standard release version? |
zen is the art of being at one with the two'ness |
|
|
|
tkontos
Junior Member
USA
13 Posts |
Posted - Nov 02 2021 : 12:36:24 PM
|
I have the same problems but not with all my projects.
I have a very small solution with a couple of small projects that works fine. My main solution (about 40 large projects with about 300K lines of code) has the problem. The VS IntelliSense works fine.
I am using VS2022 RC3 with the latest VA. |
Thanos Kontos |
|
|
|
Kaidoom
New Member
Morocco
3 Posts |
Posted - Nov 02 2021 : 2:33:31 PM
|
With VS 2019 I don't have this issue, only in VS 2022 preview 7.
Yes I'm working with 2 monitors and no I have not changed any DPI settings. And for windows I have a standard Win10 pro version.
I managed to fix the issue by having no files open when I load my solution, for this I had to disable (Reopen documents on solution load) and also wait for VA to fully load.
Also immediately closing any open tabs and waiting for VA to load also works.
So far the issue seems to be related to default intellisense suggestions list showing up before VA suggestions, if that happens I get the issue. If I open the solution and immediately start typing before VA is fully loaded then default intellisense suggestions will show up and once VA takes control, VA suggestion show up on corner.
In VS 2019 default intellisense suggestion will never show up no matter how fast I try, VA will always show suggestion once its ready.
I noticed between 2019 and 2022 the VA icon in the tool bar would go gray and back to normal again when the solution is opened, I don't see this behavior in 2019.
Hopefully some of these details help, thank you. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19054 Posts |
Posted - Nov 03 2021 : 09:11:26 AM
|
So far no sign of this problem here, but since there is a pattern on your system, hopefully we can pin down the trigger.
Can you please export your VA and IDE settings and send them to me:
VA Options -> Performance -> Export Settings
IDE tools menu -> Import and Export Settings -> Export selected environment settings
I can then import them here and see if I can reproduce the problem. Please send me the files via email:
[email protected]
including this thread ID or URL in the description, so we can match it up. |
zen is the art of being at one with the two'ness |
|
|
|
Kaidoom
New Member
Morocco
3 Posts |
Posted - Nov 03 2021 : 2:46:39 PM
|
| Thank you, I sent my settings, let me know if you need anything else. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19054 Posts |
Posted - Nov 04 2021 : 11:00:21 AM
|
I have the files, thank you for these
case=146377
So far though no sign of any problems. I have replied via email, for ease. |
zen is the art of being at one with the two'ness |
|
|
|
jorenjoestar
New Member
Italy
6 Posts |
Posted - Nov 09 2021 : 11:35:51 AM
|
Hello there,
I have the same problem and also hovering does not work at all.
In my case, having the UI in the upper left happened after I rebuilt the database (rebuild, close and reopen Visual Studio).
When reopening, I have an error loading in Visual Studio 100% of the time, and found this in the activity log:
<entry>
<record>518</record>
<time>2021/11/09 16:17:59.233</time>
<type>Error</type>
<source>VisualStudio</source>
<description>SetSite failed for package [VaCodeInspectionsPackage]Source: 'Microsoft.VisualStudio.Shell.Framework' Description: OnSettingsChanged must be called on the UI thread.#x000D;#x000A;System.Runtime.InteropServices.COMException (0x8001010E): OnSettingsChanged must be called on the UI thread.#x000D;#x000A; at Microsoft.VisualStudio.Shell.ThreadHelper.ThrowIfNotOnUIThread(String callerMemberName)#x000D;#x000A; at c1.a(Object A_0, EventArgs A_1)#x000D;#x000A; at System.EventHandler`1.Invoke(Object sender, TEventArgs e)#x000D;#x000A; at WholeTomatoSoftware.VisualAssist.Interop.VaSettings.Init(IVaService* svc)#x000D;#x000A; at WholeTomatoSoftware.VisualAssist.Interop.VaManagedService.Init()#x000D;#x000A; at WholeTomatoSoftware.VisualAssist.Interop.VaManagedService.Get()#x000D;#x000A; at WholeTomato.VaCodeInspections.VaCodeInspectionsPackage.p()#x000D;#x000A; at WholeTomato.VaCodeInspections.VaCodeInspectionsPackage.d.f()#x000D;#x000A;--- End of stack trace from previous location where exception was thrown ---#x000D;#x000A; at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()#x000D;#x000A; at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)#x000D;#x000A; at Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass20_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>d.MoveNext()#x000D;#x000A;--- End of stack trace from previous location where exception was thrown ---#x000D;#x000A; at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()#x000D;#x000A; at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)#x000D;#x000A; at Microsoft.VisualStudio.Threading.JoinableTask.<JoinAsync>d__76.MoveNext()</description>
<guid>{3606FE1F-0D41-407B-92FF-509729DA3FA6}</guid>
<hr>8001010e</hr>
<errorinfo></errorinfo>
</entry>
Configuration:
Visual Studio 2022 Version 17.0.0
VA_X64.dll file version 10.9.2435.0 built 2021.10.28
DevEnv.exe version 17.0.31903.59 Community
msenv.dll version 17.0.31902.203
Comctl32.dll version 6.10.19041.1110
Windows 10 10.0 2009 Build 19043.1288
16 processors (x86-64)
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.19041.0\cppwinrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\winrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\shared;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.29.30133\atlmfc\include;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.29.30133\include;
Other Includes:
Stable Source Directories:
C:\Program Files (x86)\Windows Kits\10\Source\10.0.19041.0\ucrt;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\src;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.29.30133\crt\src;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.29.30133\atlmfc\src\atl;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.29.30133\atlmfc\src\mfcm;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.29.30133\atlmfc\src\mfc;
This is on a small personal project.
Works fine on Visual Studio 2019.
If you need any more informations please let me know.
Thanks! |
|
|
|
bartlynn
Junior Member
USA
19 Posts |
Posted - Nov 09 2021 : 12:55:42 PM
|
I'm also experiencing the VaCodeInspectionsPackage error, but on Microsoft Visual Studio Professional 2022 (64-bit) - Current
Version 17.0.0
VA_X64.dll file version 10.9.2435.0 built 2021.10.28
DevEnv.exe version 17.0.31903.59 Professional
msenv.dll version 17.0.31902.203
Comctl32.dll version 6.10.19041.1110
Windows 10 10.0 2009 Build 19043.1320
8 processors (x86-64)
Language info: 1252, 0x409
|
|
|
|
feline
Whole Tomato Software
United Kingdom
19054 Posts |
Posted - Nov 09 2021 : 1:13:55 PM
|
The Code Inspections error is really unexpected, so it might be connected to the position problem.
Do you get this error every time you load the IDE, or just when doing a symbol database rebuild?
Do you have any other extensions installed?
Slightly randomly, have either of you enabled the setting:
VA Options -> Performance -> Use alternative directory for symbol database (requires restart)
in VS2022? What about VS2019? |
zen is the art of being at one with the two'ness |
|
|
|
jorenjoestar
New Member
Italy
6 Posts |
Posted - Nov 09 2021 : 1:17:48 PM
|
| VS2019 works fine, and for me is 100% every time I open VS2022! Thanks for the fast reply :) |
|
|
|
feline
Whole Tomato Software
United Kingdom
19054 Posts |
Posted - Nov 09 2021 : 1:21:51 PM
|
| Can you please try making a new, default C++ console solution in VS2022 and see if this makes any difference? I am wondering if somehow this is a solution specific problem. These do happen, so worth trying in case. |
zen is the art of being at one with the two'ness |
|
|
|
jorenjoestar
New Member
Italy
6 Posts |
Posted - Nov 09 2021 : 1:23:44 PM
|
Ok in my case, changing directory shows the problem only the first time (including the error message) and then if I close and reopen VS2022 it works.
Still I can't see any information when hovering on variables/methods and such! |
|
|
|
feline
Whole Tomato Software
United Kingdom
19054 Posts |
Posted - Nov 09 2021 : 1:50:55 PM
|
jorenjoestar, do you have the VA navigation bar showing? This is normally shown at the top of the editor window, and is where the Alt-M list appears. If you place the caret into a symbol, function, class, variable, is VA showing anything in this bar, or is the bar blank? VA should be showing you wha it knows about this symbol in this bar.
Assuming you have VA syntax highlighting enabled, is it actually working?
I am trying to work out how much of VA is working for you, given the lack of tooltips. Also do you have any of the options:
VA Options -> Display -> Show Quick Info tooltips for more symbols
Show additional comments when available
Show tooltips for braces and structural keywords
turned On? If they are all turned Off, does turning these options On help? |
zen is the art of being at one with the two'ness |
|
|
|
jorenjoestar
New Member
Italy
6 Posts |
Posted - Nov 09 2021 : 3:53:00 PM
|
Yes VA navigation bar showing, all the option you wrote are on.
Tried also disabling one by one them and re-enabling them.
Of course Intellisense is disabled.
If I enable Intellisense then I get the hovering from it - seems like it is totally missing the hovering from VA.
What more informations can I give you ?
Thanks for the help! |
|
|
|
jorenjoestar
New Member
Italy
6 Posts |
Posted - Nov 09 2021 : 3:57:57 PM
|
P.S. The startup error is back again. I tried running with the VA log on, so I have the va.log file ready for your view.
|
|
|
|
r.khlebnikov
New Member
2 Posts |
Posted - Nov 10 2021 : 10:37:09 AM
|
| I'm having exactly the same issue with the location of suggestions after upgrading from VS 2022 preview 5 to VS 2022 release version. Please advise. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19054 Posts |
Posted - Nov 10 2021 : 11:09:07 AM
|
r.khlebnikov are you just getting the problem with listboxes appearing in the wrong location, or are you also getting other problems as well?
Which version of VA are you using? VA build 2435.0 has better support for VS2022, but it was possible to use earlier versions of VA as well. None of them should cause this problem, but its somewhere to start. |
zen is the art of being at one with the two'ness |
|
|
|
r.khlebnikov
New Member
2 Posts |
Posted - Nov 11 2021 : 09:00:47 AM
|
I'm actually also getting the Code Inspections error at startup as well. My full info is below.
License: Standard (**REDACTED**) Support ends 2022.03.02
VA_X64.dll file version 10.9.2435.0 built 2021.10.28
DevEnv.exe version 17.0.31903.59 Professional
msenv.dll version 17.0.31902.203
Comctl32.dll version 6.10.19041.1110
Windows 10 10.0 2009 Build 19042.1288
8 processors (x86-64)
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.19041.0\cppwinrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\winrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\shared;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um;
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Auxiliary\VS\UnitTest\include;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt;
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Auxiliary\VS\include;
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.30.30705\atlmfc\include;
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.30.30705\include;
Other Includes:
Stable Source Directories:
C:\Program Files (x86)\Windows Kits\10\Source\10.0.19041.0\ucrt;
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Auxiliary\VS\src;
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.30.30705\crt\src;
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.30.30705\atlmfc\src\atl;
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.30.30705\atlmfc\src\mfcm;
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.30.30705\atlmfc\src\mfc;
|
|
|
|
ChrisG
Whole Tomato Software
USA
299 Posts |
Posted - Nov 11 2021 : 12:51:35 PM
|
| I was able to reproduce the issue and have opened case 146405 to get this looked at. Thank you everyone for making reports of the problem. |
|
|
|
FrozenInMTL
New Member
Canada
3 Posts |
Posted - Nov 11 2021 : 5:11:59 PM
|
By any chance do you have a workaround for this?
Thanks! |
|
|
|
ChrisG
Whole Tomato Software
USA
299 Posts |
Posted - Nov 11 2021 : 5:34:56 PM
|
Yes, please try unchecking the following in the Visual Assist options dialog. This will disable our suggestion lists and should restore the normal UI position.
Workaround: Extensions > VAssistX > Visual Assist Options... > Suggestions > Enable in C++ (Uncheck) |
|
|
|
FrozenInMTL
New Member
Canada
3 Posts |
Posted - Nov 11 2021 : 5:46:09 PM
|
| Thanks! We can safely ignore the VaCodeInspectionsPackage error? |
|
|
|
ChrisG
Whole Tomato Software
USA
299 Posts |
Posted - Nov 11 2021 : 6:04:35 PM
|
| I wouldn't say safely. The error could cause issues such as Code Inspections failing to work. |
|
|
|
FrozenInMTL
New Member
Canada
3 Posts |
Posted - Nov 15 2021 : 10:07:42 AM
|
| Thanks! We can safely ignore the VaCodeInspectionsPackage error? |
|
|
|
feline
Whole Tomato Software
United Kingdom
19054 Posts |
Posted - Nov 15 2021 : 12:50:10 PM
|
When you get the package error, can you see if Code Inspection still works correctly, or if it is no longer working?
If you are seeing the VaCodeInspectionsPackage error, which OS are you using? I have another report of this problem under Windows 11, so I am trying to work out if the OS could be a factor. So far no success in triggering this error here, so I am not sure what the trigger might be. |
zen is the art of being at one with the two'ness |
|
|
|
sosedada
Senior Member
USA
36 Posts |
Posted - Nov 15 2021 : 12:58:11 PM
|
I'm using Windows 10 Enterprise 19042 and also see this issue.
I haven't flushed anything since upgrading from VS2019 to VS2022, so perhaps that's the issue, and my projects are all fairly old. I've seen this since the first time I installed 2435.
Code Inspections do not work, after re-enabling them in the options dialog. Just silent failure. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19054 Posts |
Posted - Nov 16 2021 : 08:01:48 AM
|
Thank you for the update, so not OS specific, that's good to know.
Are you getting this error every time you load VS2022? It sounds like you are. If so, can you please try making a new, default C++ solution and see if you get the same error when loading the test solution? I doubt that this error is solution specific, and it definitely seems to be random for some users, so if you are seeing this every time that should make it quite a lot easier to study and try to make sense of. |
zen is the art of being at one with the two'ness |
|
|
|
sosedada
Senior Member
USA
36 Posts |
Posted - Nov 16 2021 : 09:23:37 AM
|
| Creating a new console application does not error and inspections work after enabling. Continues to work after restart. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19054 Posts |
Posted - Nov 16 2021 : 09:28:14 AM
|
Thank you for testing that. I didn't really expect that result, so that's interesting.
Which language or languages does your main solution use?
How many projects does the solution contain?
Does triggering a VA symbol database rebuild have any effect on this?
VA Options -> Performance -> Rebuild symbol databases
this will take a couple of minutes when you load your solution, possibly longer if you have a very large solution or number of stable include directories. I would not expect this to help, but it might.
If you use a Windows File Explorer window to look in the directory where your .SLN file lives you should see a ".vs" folder. This folder contains the IDE symbol database from IDE intellisense.
If you close the IDE, and then rename (to be safe) this directory and then load your solution again, does this have any effect? I have occasionally seen a corrupt IDE symbol database cause strange problems, so its worth testing. |
zen is the art of being at one with the two'ness |
|
|
|
Topic |
|
Suggestions list appears top left
