Intellisense does not show suggestions
See original GitHub issueMVC Core applpication
dotnet --info
output:
VS Code version:
C# Extension version:
Steps to reproduce
I create a simple model class with attributes, the intellisense do not suggest add the using class and cannot detect the error
Expected behavior
Actual behavior
Issue Analytics
- State:
- Created 6 years ago
- Comments:28 (14 by maintainers)
Top Results From Across the Web
Visual Studio C# IntelliSense not automatically displaying
Open Tools > Options > Text Editor. If you're only having this issue with one language, find that language; if it's for everything,...
Read more >Visual Studio IntelliSense Not Working? What To Do.
If all of the above didn't work, it's time to verify some configurations in Visual Studio itself. Go to Tools -> Options ->...
Read more >IntelliSense not working in VS Code - The Windows Club
If IntelliSense is not working as it should on your Windows 11/10 PC, you can try restarting VS Code and this should solve...
Read more >How To Solve IntelliSense Not Working In VS Code
Method 1: Reload The VS Code · Method 2: Check If IntelliSense Is Installed · Method 3: Restart And Update VS Code ·...
Read more >C# - Visual Studio Code Intellisense (autocomplete) not working
... but Visual Studio code Intellisense (Autocomplete) suggestion is not working correctly, and doesn't show any suggestions when using ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Let me know if you have anymore trouble.
OK. So it sounds like things are working for you.
By launching VS Code from a VS 2017 Command Prompt, that provides enough context that to initialize an MSBuild build environment. This can be necessary to handle situations where there are several versions of Visual Studio installed. The VS 2017 Command Prompt sets two environment variables that can help MSBuild “find” itself:
VSINSTALLDIR
: The path to VS, which could be something likeC:\Program Files (x86)\Microsoft Visual Studio\Preview\Enterprise\
. This will depend on where VS 2017 is on your machine.VisualStudioVersion
: Set to15.0
.If you like, you can set these environment variables to correct values before launching VS Code.
Note that VS Code’s editor experience is not identical to Visual Studio. It’s not clear to me exactly what you’re describing, but it sounds like you may have encountered one of the differences between the products.