I am using Visual Studio Community and Visual GDB to code and debug STM32 projects.
The problem:
When I type something that is known to Intellisense, (path, variable or anything really), the suggestions come up briefly and then immediately disappear therafter. For that split second I can see that Intellisense has the correct suggestions, but TAB or ENTER does not work since the suggestions disappear very quickly.
Does anyone know how to fix this?
Thank you
You might try to disable any extensions in Visual Studio.
I had the same problem, surfed around and read in some places that disabling extensions would work.
So I disabled them one by one and the problem was gone.
Related
I am new to Visual Studio and would like to disable the IntelliSense automatic suggestions without disabling IntelliSense entirely. More precisely, I don't want popup hints continually covering the code I'm working on, but I'd still like to be able to use Ctrl-Space to request suggestions at times. I'm coding in C/C++.
I've seen information on how to do this for Visual Studio Code, but I haven't found anything similar for Visual Studio.
Or if this is just a matter of me not understanding how to properly use Visual Studio or IntelliSense, please help me understand or point me to a forum where true Microsoft devotees hang out.
The solution is to go to Tools -> Options -> Text Editor -> C/C++ -> General and uncheck Auto list members.
Credit goes to this answer in "Intellisense “Toggle Completion Mode” doesn't work with C++ in Visual Studio 2010 Professional".
Turning off auto-suggestions in Visual Studio 2019 without turning off
IntelliSense
Solution
Edit Menu-->Intellisense-->click Toggle Completion Mode
After that, when you type, it will not cover the code you are working on automatically.
Hope it could help you.
Mabby this can help you this is a article i found about this
https://www.technipages.com/visual-studio-turn-off-autocomplete
My first question on SO, so please be gentle ;-)
As per the title, when I open any solution in Visual Studio 2013, the solution is opening in an unbuilt state, reporting lots of errors etc. I haven't been able to track anyone else down having the same issue on SO, and have already been through nearly all the VS->Tools->Options and compared with a colleague's settings, but not found a solution so far. As soon as I press Ctrl+Shift+B the solution builds and all errors go away.
At the moment this isn't such an issue as the solutions and projects are all relatively small, but when we do return to one of our larger projects, the added delay will become annoying.
Thanks
Stuart
Turns out the sea of red is in fact Resharper complaining and not Visual Studio.
Have tried various fixes as per this link ReSharper "can not resolve symbol" even when project builds, but still not resolved.
For now have turned off code inspection in Resharper.
I have got the following problem with F# code recently: almost the complete code is underlines with curly red lines (indicating problems) and whenever I hover with the mouse cursor over any word the pop-up appears with the message "Unexpected token". IntelliSence doesn't work either.
Nonetheless if I start the project it is executed without any problem.
This happens both to already existing F# files and to newly created F# projects. I remember it was working just 2-3 months ago!
I tried to deactivate all possible extensions but it doesn't help.
Any ideas?
I get this too. Sometimes, simply exiting and going back into VS helps. When I tweeted the problem, Don answered with this:
"do you have "python tools for visual studio alpha" installed? if so, uninstall it or apply the hot fix"
This wasn't relevant to me (as I haven't been anywhere near python) but I'm posting here in case it helps you.
-- Edit: here's a link to the patch, thanks to Alexander Galkin: http://pytools.codeplex.com/workitem/599
I haven't seen this situation before but here's a guess at why it's happening and how you might cure it.
Visual studio works on a system for plugins. Even the stuff that is "native", like the C#/F#/VB.NET project systems, are just plugins that uses the visual studio shell. It looks like the F# plugin has been damaged in someway.
If this is Visual Studio 2010:
You might try opening the visual studio installer and trying a repair installation or deactivation and reactivating the F# project system
If this is Visual Studio 2008:
You might try uninstalling and reinstalling the F# plugin
I have been a fan of the new "Navigate To" feature that was released with Visual Studio 2010 since I saw Scott Hanselman using it in one of his presentation.
For some unknown reason, it randomly stops working.
I hit "Ctrl + ,", type what I am looking for and then nothing happens.
It seems to wait for something and the window shows no progression in the research.
The only way I found to fix this is to restart Visual Studio and wait for the problem to happen again.
Does anyone have any idea why Visual Studio is behaving like this and how I can fix this?
I got this working by simply selecting an item from the Search Items dropdown. Once you do that, the search starts working again as expected.
I got this working again by uninstalling ReShaper. It fixed some other things like the solution wide search aswell. I'm not so happy about the solution though...
Any chance you're using resharper, powercommands, or productivity power tools?
I suspect the issue is related to one of those (I have the same issue), but since it's difficult to reproduce, it's hard to test that.
Today my Visual studio couldn't help me by auto complete so I thought that the ReSharper trial period had ended .After I suspended ReSharper I see that still no auto complete. After a few changes I see still the same problem and there are some strange behavior in Visual Studio. For example I see m_value field for int. But my other Visual studio instances works as expected. How can I fix this problem?
Probably there is an error somewhere in your code which is causing the types to be determined incorrectly - for example a missing curly brace. Check your code carefully for errors. Make sure that your code compiles correctly.
PS: You don't need ReSharper to get autocompletion. Intellisense is a standard feature of Visual Studio. Even without ReSharper I find the built-in autocompletion extremely usable.
IntelliSense is Microsoft's implementation of autocompletion, best known for its use in the Microsoft Visual Studio integrated development environment.
The file property build action was content and this was reason of those strange behaviours. It is fixed after turned build action to compile.