How to get intellisense in Visual Studio Code for Unity functions names?

Question

I am following a tutorial about Unity and I see that the instructor has intellisense when writes the method's name.

However I have only intellisense with classes and variables, I mean Unity classes like Rigidbody and my own variables.

I have also read: Autocompletion not working in Visual studio

How to enable intellisense in Visual Studio 2017 for Unity

Answer 1

Old question, but I had the same problem just recently.

There must have been an issue in your Assembly-CSharp.csproj or project-name.sln files. Most likely to be the .csproj file. If you take a look at it, you will see various references to .dll files.

You can tell Unity (my version: v2019.2.20f1 ) to create these for you by enabling Edit > Preferences > Generate all .csproj files.

 1. Delete both files.
 2. Enable .csproj file generation.
 3. Double click on a script in Unity.

This fixed my issue.

Answer 2

Although the answer by Alex Myers is helps, its not 100% right. Unity Snippets does give you some snippets, and the illusion of typeahead, it's not actually intellisense.

For true intellisense you need to:

• install dotnet on your system ( https://code.visualstudio.com/docs/languages/dotnet ) and,
• install the dotnet extension for VSCode ( https://marketplace.visualstudio.com/items?itemName=ms-vscode.csharp )

More information can be found here: https://code.visualstudio.com/docs/languages/dotnet

You can test you have dotnet installed by typing dotnet into the terminal within VSCode.

Note In the image below how I get a full method signature, reference counts, and the yellow hint globe. These are only available when using dotnet + extension (and not available when using the snippets)

Answer 3

I would really like to clear things up a bit for everyone trying to get intellisense working with Visual Studio Code.

First of all I am writing this for Unity 2019.4.14 as it is the newest version.

These are the things you MUST do for this to work:

1. You need Visual Studio Code (duh)
2. The .NET Framework Dev Pac (not just the .NET core, not even the .NET core SDK, but the Framework Dev Pack because otherwise VSCode is going to be throwing this error:

The reference assemblies for .NETFramework,Version=v4.7.1 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application.

3. Check if you have .NET installed by typing dotnet in the VSCode terminal.
4. In VSCode search for the 'C# for Visual Studio Code' extension and install it
5. In Unity go to Package Manager and install Visual Studio Code Editor. This will enable Unity to generate proper project files for VSCode.
6. In Unity go to Edit -> Preferences -> External Tools and choose VSCode from the dropdown (could be listed as code.cmd) and after you choose it tick all the checkboxes you want in the Generate .csproj files for section. I checked Embedded Packages, Local Packages, and Packages from unknown sources. Click 'Regenerate project files'
7. Open any C# file from Unity and you should be good to go.

Now, what about Unity Code Snippets and Debugger for Unity extensions? Well these are useful helper extensions but they have nothing to do with Intellisense. The first is for quickly typping common Unity patterns and the second is for showing Unity Debug warnings and errors as you type instead of saving and going back to Unity and reading the console.

Hope this was of any help.

Answer 4

Check out the guide for Unity Development with VS Code . They recommend a few extensions:

• Unity Snippets
• Debugger for Unity
• Unity Tools

I believe the Unity Snippets extension is what you are looking for.

Answer 5

Note: my solution does not solve intellisense to function names, but this was the first question that come in fixing intellisense more generally in VSCode.

I needed to update the VSCode package in unity .

In Unity, click Window, then Package Manager, then look for Visual Studio Code Editor. Expand it by pressing triangle, and upgrade to the latest version (for me, it was 1.2.0 . I restarted VSCode and it worked.

v1.1.4 had a bug that caused this problem, and was not fixed for about 3 months. It is still the default package installed with a new default project, so you have to change this package version to 1.2.0 in every new project, until they update it.

Answer 6

Intellisense is a pure workflow of .Net Environment. So, you need to have .Net 'Developer pack' (not Runtime) installed on your system as it installs all three necessary components below:

1. .Net framework
2. .Net Target pack
3. .net SDK

reference link: https://dotnet.microsoft.com/download/visual-studio-sdks

It is directly installed to a system admin-accessible path, so no need setting it up. Now, you have to tell VS Code which .Net version to use (whichever you have installed). Your Unity project will have these two files in the root directory:

1. Assembly-CSharp.csproj
2. Assembly-CSharp-Editor.csproj

In these both files search for line (probably 16):

<TargetFrameworkVersion>v4.8</TargetFrameworkVersion>

Edit version that you had just installed (I had 4.8). Then reopen VS Code. Now everything should work fine.

Answer 7

对我来说只是在 Unity 中， Edit/Preferences/External Script Editor ，并将其更改为My_Install_Location\\Microsoft VS Code\\Code.exe （可能点击 Regenerate Project Files）

Answer 8

Sorry, I don't have good English, but I'll show you what worked for me.

I opened the C # script in Visual Studio Code and looked for the Assembly-CSharp.csproj file, then, on line 16, I changed the following:

<TargetFrameworkVersion> v4.5 </TargetFrameworkVersion>

For:

<TargetFrameworkVersion> v4.5.1 </TargetFrameworkVersion>

This solved the Intellisense issue.

Answer 9

I found another solution since none of the other solutions were working for me and i was searching for hours.(07/08/2021):

I got the feeling i found the solution for a lot of people since i reinstalled windows recently and simply downloaded everything needed to start without other problems.

I got the same error with .NET, .NET Core or .NET Framework, here are some screenshots of the errors:

In the error output, it says to install the Developer Pack for this framework version. You can find the version in the .csproj file:

By installing the .NET Framework of this version on the dotnet microsoft site: .NET Framework download list i fixed the error after reloading VSCode and got my Intellisense working for Unity.

TLDR: My fix was too install .NET Framework version 4.7.1

Answer 10

Though the question is 2 years old, the problem pops up occasionally, just like happened to me.

I had the issue myself, so this one is possibly the first that should be checked.

• "Install .NET Framework 4.6 Targeting Pack"

WHY?

First of all, I work with dotnet core, not the standard, so I don't have standard libraries installed on my computer. When I started trying Unity, and VS Code with it, this was the missing part I wasn't aware of.

When I hit the issue, I searched the net a while and see this question. Took me another while to notice this framework sentence in "Enabling code completion" section of VS Code and Unity page. So I tried and now I am happy I tried.

Just don't forget you need to restart at least VS Code to get the intellisense working.

PS: Framework version may, and will most possibly, be changed depending on what year we are in, and which versions we use. So if "4.6" is not working then you probably need another version.

PS2: If it is Mac you are looking for, follow the same link above and find the same section I mentioned above to get a link for .NET SDK.

Answer 11

Follow these steps:

1. Go into your Unity project.
2. Go to Edit .
3. Go to Projects preferences .
4. Go to External tools .
5. In line "External Script Editor" you have to change to "Visual Studio Cummunity 2019..."

then it should work.

Answer 12

对于在Mac上遇到相同问题的任何人，请尝试在您的.vscode/settings.json （或在用户设置而不是工作区设置中）设置此值

"omnisharp.useGlobalMono": "always"

Answer 13

If you still can't enable IntelliSense, make sure you have VS Code opened in the same directory as the .sln file (I had mine opened deeper in the Assets before).

Source: https://code.visualstudio.com/docs/other/unity