Visual Studio C # IntelliSense does not automatically display

Most recently, my Visual Studio 2010 stopped displaying IntelliSense suggestions automatically during input. I can still press ctrl + space to make it work, but it does not automatically display the list of offers to which it is used. I already tried disabling all my extensions, restarting VS and the computer, and I checked all the relevant settings (Options β†’ Text Editor β†’ C # β†’ IntelliSense) to make sure that it is configured to offer sentences after the character is typed.

Has anyone seen this behavior before? Does anyone have any other suggestions on how I can get IntelliSense to go back to what it was before? If not, I just need to do a new VS reinstall ...

+49
c # visual-studio-2010 intellisense
Dec 07 '11 at 18:11
source share
14 answers

enter image description here




In prose, if you do not see the image above:

Go to Tools> Options> Text Editor. If you have this problem in only one language, find this language; if this is for everything, click "All Languages". At the top of the screen there will be several options with the words "Automatic list items", "Hide advanced items" and "Parameter information". Make sure all of them are turned on (although the second can be turned off, if so, ignore it).

+103
Dec 07 '11 at 18:55
source share

I found that sometimes even checking the settings in the "Parameters β†’ Application Filling" section (answer above) does not work. In this case, saving and restarting Visual Studio will enable Intellisense again.

Finally, this link contains a list of other Intellisense troubleshooting methods broken down by language (for more specific errors).

http://msdn.microsoft.com/en-us/library/vstudio/ecfczya1(v=vs.100).aspx

+16
Oct. 30 '13 at 18:07
source share

I will start with the fact that this did not happen, since I updated my RAM. I was in 4 GB and often had multiple VS open instances along with SSMS. Since then I switched to 8 GB and then to 16 GB.

Here are the steps that I follow when I lose intellisense.

If only one file / window is affected, close / reopen this file. If this does not work, try below.

In Visual Studio:

  • Click Tools-> Options-> Text Editor-> All Languages-> General
  • Uncheck "Automatic list items"
  • Uncheck "Parameter Information"
  • Check the box next to "AutoLinks" (yes, the one you just shot)
  • Check "Parameter Information" (again, the one you just shot)
  • Click OK

If this does not work, try a few more steps:

  • Close all VS documents and reopen
  • If still not working, close / reopen the solution.
  • If still not working, restart VS.

For C ++ projects:
There are a few things you can try on MSDN : MSDN Suggestions

It looks like a damaged .ncb file.

From MSDN:

  • Close the solution.
  • Delete the .ncb file.
  • Reopen the solution. (This creates a new .ncb file.)

Notes:

  • This issue is not specific to C #, since C ++ and VB users report the same issue

  • Tested on VS 2013/2015

+5
Feb 04 '16 at 15:26
source share

Steps to fix:

  Tools Import and Export Settings Reset all settings Back up your config Select your environment settings and finish 
+3
Mar 11 '14 at 11:30
source share

I also ran into the same problem, but in VS2013.

I made the following way to fix, it worked fine.

  • Close all open instances of Visual Studio.

  • Then go to the " Developer Command Prompt ) from visual studio tools,

  • Enter it as devenv.exe /resetuserdata

  • Restart your computer, open Visual Studio. Then he will ask you to choose development parameters from the very beginning and after that open any solution / project. You will be amazed.

Hope this can help you :)

+2
Jan 08 '15 at 6:10
source share

Sometimes I found Intellisense slow. Hit the. and wait a minute and see if it appears after the delay. If so, then I believe that there may be a cache that can be deleted so that it can be re-launched.

+1
Dec 07 '11 at 18:19
source share

I find this today after the following sequence:

  • Added a new class to my project.
  • Closed Visual Studio but randomly selected No when she asked if I want to save the changes.
  • Reopened Visual Studio and found that it automatically opened a new file, but without my previous changes (as expected). However, IntelliSense no longer worked in the new file.

The problem was not to save the changes in the new file, this did not save the changes in the project, so after reopening Visual Studio the file was not part of the project. The command Show all files in Solution Explorer or Add β†’ Existing item ... resolved the problem.

+1
Jan 29 '14 at 21:14
source share

I had a file excluded from the project, so I could not debug and have intellisense in this file. Including the file back into the project solved my problem! :)

+1
May 26 '15 at 10:17
source share

.suo file in the solution folder to resolve the problem.

+1
Jun 15 '15 at 14:15
source share

I just closed all the pages of the visual studio and reopened .. and worked.

0
May 05 '16 at 5:37
source share

Deleting the .vs folder in the solution solved my problem. You must exit Visual Studio and then delete the .vs folder and run Visual Studio again.

0
Jan 11 '18 at 6:05
source share

This may be due to a change in solution configuration to Release Mode instead of debugging. Right-click the solution -> Properties -> Configuration Properties -> Set Configuration for Debugging, if it is in version.

0
Mar 02 '18 at 6:07
source share
  • Closed all my windows VS
  • Launched the Visual Studio installer and clicked "Change."
  • Under Individual Components> Code Tools> Uncheck NuGet Package Manager and select it again.
  • After changing and restarting, VS IntelliSense worked correctly again.

Found my answer at https://developercommunity.visualstudio.com/content/problem/130597/unity-intellisense-not-working-after-creating-new-1.html

0
Jan 17 '19 at 15:14
source share

In the era of the .net kernel, a new reason for this is to download a project for an unsupported version of the .net kernel. For example, if you downloaded a project from GitHub that was configured to use:

  <PropertyGroup> <TargetFramework>netcoreapp2.2</TargetFramework> <AspNetCoreHostingModel>InProcess</AspNetCoreHostingModel> </PropertyGroup> 

But you only have 2.1 installed or you are using Visual Studio 2017, then the compiler will not be able to find the SDK code and thus provide intellisense.

The solution in this case may be to right-click on your project and select Edit MyProject.csproj from the context menu and change the target environment if necessary:

  <PropertyGroup> <TargetFramework>netcoreapp2.1</TargetFramework> <AspNetCoreHostingModel>InProcess</AspNetCoreHostingModel> </PropertyGroup> 

This assumes that any project you uploaded can indeed be launched within the framework of the previous target platform.

0
Jun 15 '19 at 1:04 on
source share



All Articles