Visual Studio Code's more advanced editing features (IntelliSense, refactoring tools, etc.) only work in C# files if you have a project.json file or *.sln file that VSCode is aware of. Open the folder (i.e. open the File menu and click Open Folder...) with the *.sln file or project.json and VSCode will attempt to find all project/solution files in the folder. If there are multiple projects, you may need to select one from the projects button on the right side of the status bar (bottom of the window).

From the VSCode website:

• Selecting a project.json-file is opening a DNX-project and VSCode will load that project plus the referenced projects
• Selecting a *.sln-file is opening a MSBuild-project. It will load the referenced *.csproj-projects and sibling or descendant project.json-files but no other project files that are referenced from the solution file.
• Selecting a folder will make VSCode scan for *.sln and project.json files and VSCode will attempt to load them all.

As of the 0.5 version I have found that I need to close and re-open my working files to get some new intellisense information to start working for my own files. This usually happens after I have a file open that needs to use type information from another file I just created. Until I close and re-open them (within the editor) the intellisense doesn't always work.

Hopefully this is something that'll get fixed as the app matures.

Try "Install Extension" from command Pallete - probably if C# intellisense is not there:

https://code.visualstudio.com/docs/customization/colorizer

I've had some good experiences in C# with this extension so far: https://marketplace.visualstudio.com/items?itemName=jchannon.csharpextensions

This extension traverses up the folder tree to find the project.json or *.csproj and uses that as the parent folder to determine namespaces.

Inorder to make the intelligence working, the Visual Studio Code extension OmniSharp should be there along with Mono. When you open a project/solution folder, the OmniSharp gets the project dependencies from either project.json or from the dotnet solution file (if the project/solution created with other versions of visual studio).

So, when you look at the omnisharp's output window after immediately opening the project/ solution folder, you may see the following lines

Starting OmniSharp server at 2017-9-18 09:26:44
Target: /Users/{username}/Source/{Your Solution Folder}/{Your Solution
file}.sln


OmniSharp server started wth Mono
Path: /Users/{username}/.vscode/extensions/ms-vscode.csharp-1.12.1/.omnisharp/run
PID: 5808

post that, you may see couple of lines coming up like below,

[info]: OmniSharp.MSBuild.MSBuildProjectSystem
Update project: {Your Project1 Name}
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
Update project: {Your Project2 Name}
....

they mean that your projects are getting recognised by OmniSharp Extension.

If you get any error message informing you about timeout, please get into the settings of the Visual Studio Code, and add a configuration override like the one below:

  "omnisharp.projectLoadTimeout": 200

I know it is too long to wait for 200 seconds. But don't worry, this won't stop you anymore working with project files. But, remember that the IntelliSense will be automatically available once all the projects in the folder are successfully loaded.

Feel free to extend the Timeout setting since it will help you getting intellisense even-though you are not getting it immediately.

Here is another link with the same solution: https://github.com/OmniSharp/omnisharp-vscode/issues/1585

Hope my information helps you! Enjoy your VSCode!

Another troubleshooting strategy to try if none of the above works out is uninstalling Mono, which is unnecessary anyways if you're using .NET Core. I also experienced a sudden disappearance of Intellisense after pulling changes to one of our enterprise repos that included an upgrade from ASP.NET Core 2.0 to 2.1. Strangely, at the same time, Intellisense was working fine in another C# project repo running ASP.NET Core 2.2.

For the project in question, I was puzzled to see successful logs for each reboot of the Omnisharp server as well as perfectly clean builds and runs. The puzzlement increased as I compared these Omnisharp logs to those from the 2.2 project and found them effectively identical.

Upon uninstalling Mono, the one detail that changed is how Omnisharp started. Now it boots up from a shell script located at ~/.vscode/extensions/ms-vscode.csharp-1.19.0/.omnisharp/1.32.18/run. Previously, Mono itself was booting the server from the executable at ~/.vscode/extensions/ms-vscode.csharp-1.19.0/.omnisharp/1.32.18/omnisharp/Omnisharp.exe.

Other troubleshooting I attempted in this instance though to no avail:

• dotnet clean / Deleting bin and obj directories
• Updating launch.json to point at the proper /bin/Debug/netcoreapp2.1 build directory
• Wiping my local nuget cache
• Restarting Omnisharp
• Uninstalling and reinstalling VS Code, as well as bumping back a version from 1.33.1 as the breakage coincided oddly with the March 2019 update
• Uninstalling and reinstalling the C# VS Code extension, as well as bumping back a version from 1.19.0 given other users' reports of said version interfering with Intellisense for certain projects*
• Adding a global.json file at project root to override default utilization of latest .NET Core SDK (mine was 2.2.105) and run instead using 2.1.302 in concert with the project's version
• Wiping/rebuilding the project .sln file

Specs: VS Code 1.33.1, C# Extension 1.19.0, MacOS High Sierra 10.13.6.

*NB: As it turns out, in another .NET Core 2.1 project with the same issues in VS Code as described above, uninstalling Mono alone did not fix things. I also did wind up needing to bump back the C# extension to v. 1.18.0 to recover Intellisense. Weird.

This case was for an existing project that was working fine before. Opened via the vs code "recent" history.

For dotnet core. I opened my project's *.csprog file, made no changes, and saved it via the vs code editor.

As soon as I saved, all of the intellisense stuff starting working again in my other files within that project.

After trying several things I looked at the OmniSharp logs only to realize that because I had two different sln files in my workspace. It had picked up the “other” one and thus wasn’t working. I deleted it, reopened vs code, and all is well again.

For me I had been working without internet for a long time. It had previously been working but then stopped. I closed+reopened VSCode with a stable wifi connection and the Output tab in VSCode popped up, displaying the the extensions were re-installing. After that it worked!

If you have a workspace and for some reason have multiple folders you may need to 'help' omnisharp a bit. I initially had a big project and added a solution for it further on - ending up with TWO workspace folders (one to a startup project and one to the solution). After composing that setup I experienced only the first project to have intellisense working.

Solution to get intellisense working was to make sure omnisharp worked its way from the solution instead of the project:

1. Ctrl + Shift + p
2. Write "OmniSharp: Select Project" and press Enter.
3. Choose the solution workspace entry.

Inspiration gotten from 'swaner': https://github.com/OmniSharp/omnisharp-vscode/issues/1889

in my case , the extension wasn't enabled

Clearing typescript cache and downgrading the typescript version to 3.3 solved the issue for me.

Follow these steps to clear cache and downgrade typescript version:

1. Enter following command in terminal according to your OS and delete whatever is inside it.

• Mac: ~/Library/Caches/TypeScript/
• Windows: %LOCALAPPDATA%\Microsoft\TypeScript\ (windows users can run this in run box too)
• Linux: ~/.cache/typescript/

2. Install this specific @typescript@3.3 using following command.

• npm install -g typescript@3.3

3. Restart VSCode.

if intellisense in not working for react js or javascript or node js this solution will help for windows

1. uninistall type script by typing npm uninstall -g typescript
2. install specific version of type script that is 3.3 by typing npm install -g typescript@3.3
3. add the typescript location in vscode by navigating to file > Preferences > settings > here search for edit in setting.json then add this path "typescript.tsdk": "/Users/yourusename/AppData/Roaming/npm/node_modules/typescript/lib"
4. settings.json should look someting like this

{
"editor.suggestSelection": "first",
"vsintellicode.modify.editor.suggestSelection":"automaticallyOverrodeDefaultValue",
"typescript.tsdk": "/Users/yourusername/AppData/Roaming/npm/node_modules/typescript/lib"
}

I just had this happen (this being no code completion suggestions appearing). What resolved it for me was changing the VSCode Editor package in Unity to a previous version and then back to the current version.

For me, this was going from 1.2.0 to 1.1.3 and then back to 1.2.0. I believe removing and reinstalling 1.2.0 would have accomplished the same.

Window > Package Manager > Visual Studio Code Editor

I know this is probably the most obvious answer. But I had enough dealing with VS Code ridiculous bugs. You should be focusing on code, not the buggy IDE. Their documentation doesn't make it easy either to debug.

Steps for complete uninstallation:

1. Save your personalization files such as keybindings.json,

Just put it on GitHub or something so whenever you need have trouble with VS Code you simply just need to go to GitHub and copy-paste it.

2. Uninstall VS Code completely

When you uninstalled VS Code, it doesn't erase your extension files and some old settings. This is the cause of the re-installation ended up the same. Horrible move VS Code. For the list of the files that you must delete, you can check out this answer.

3. Go to their website and install the new one.

I hope this helps some people who are already had enough with the VS Code ridiculous bug.

In my case, the issue was not with VS Code settings. The error was due to a corrupted TEMP path configured in my PC's registry user profile environment settings. I got this error from Help --> Toggle Developer Tools --> Console The error was flagged in the console when I opened a new typescript file.

Unable to write file c:\Users\XXX\AppData\Local\Temp;C:\wamp64\bin\php\php5.6.25;C:\vufind-3.1.2\install.php\09cf49d8-af5b-42e9-8194-43f5b566be0f'

Obviously this path was corrupted. After updating the environment variables in registry settings, the VS code IntelliSense started working. Checking the console is a good start to find the root cause of this issue.

I was able to fix this by changing the Api Compatibility Level from .Net Standard 2.0 to .NT 4.x. You can find this setting on Project Settings / Player. After that, intellisense started working again.

This is because of C# extension issue. Reinstall the extension will work.

https://code.visualstudio.com/docs/editor/intellisense

https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csharp

The issue I had was OmniSharp was an older version. I set the flag to update to latest version in Settings.json file. This ensures the extension is always the latest version.

"omnisharp.path": "latest"

And restarted VS code. That fixed it for me.

Simply reinstall the extension and restart the VSCode/PC.

Earlier intellisense was working for Angular in VS-Code but for some reason (which I don't know) intellisense stopped working. I had extensions installed i.e. Angular Essentials and Angular Language Service etc. that were responsible for this intellisense and all that.

What I did?

I disabled the extensions, restarted VS Code and enabled them. It was all working fine as before.

I use Task Manager and kill the Visual Studio Code process, then restart Visual Studio Code, the intellisense shows and fixed.

If everything in VSCode is working ( No errors in output console, language server is working etc.) and built-in extensions are enabled. Still, if your IntelliSense is not working for normal .js files make sure variables are defined with a type identifier such as var d = new Date() or let d = new Date(). In my case, IntelliSense was not working for d = new Date() (No autocomplete for Date object 'd' APIs in this way) but started working fine when I specified a type before my variable names.

Download and install "Tool for Visual Studio 2019" as the C# extension under hood use the build tools: https://visualstudio.microsoft.com/downloads/

In my case, I had an extension installed (Explorer Exclude) to help me focus and hide certain files that I don't regularly work with within the Explorer.

I so happened to have disabled viewing *.sln, *.csproj and *.vsconfig files and folders, which apparently prevents VSCode from even knowing the file is there in the first place. Disabling these specific rules solved the problem instantly.

Took me ages to figure out... The more you know.

Downgrading to 1.23.9 of the C# VS Code extension fixed the intellisense for me. So if nothing else is working for you, perhaps try installing an older version of the extension (doesn't necessarily have to be that exact one I mentioned). You can do this by selecting this option in VS Code:

If you are start your project with c#, then some time you haven't download extension.

Process by written

• Ctrl + Shift + p.
• Write "OmniSharp: Select Project" and press Enter.
• Choose the solution workspace entry.
• Then enable the c# extension for "OmniSharp : Project".

Process by image

I fixed this with a multiple project solution in .net5 / .net core 3.1 by opening each project (not the sln folder) in VSCODE. This then prompts to add the resources/ .CSX? files to the project; enabling intellisense, per project. Finally close that window and reopen the solution folder and all works as expected.

See image Add VSCode assets

I solved it by uninstalling all SDK's (not sure if this is needed) and installed 4.7.1 developer pack

win 10, vscode 1.63.2, unity 2020.3.25f1

I fixed this by installing .NET Framework 4.7.1 Developer Pack:

https://dotnet.microsoft.com/en-us/download/dotnet-framework/net471

Downgrading to 1.23.9 of C# for Visual Studio Code (powered by OmniSharp). https://i.stack.imgur.com/VrdJl.png