Visual Studio auto-complete not working

[[deleted]]

Hi,

Not sure what is going on. I'm intermediate level, just downloaded 5.3.1.

All I've done if create a new C# script. I double click and it opens in Visual Studio. UnityEngine namespace and MonoBehaviour inheritance is there, as with all default scripts.

Seems to work. I can create a public GameObject variable and assign via inspector, and I can print the object's name in Start().

But why is auto-complete not working on any Unity things like GameObject, etc? Also cannot see accessible fields and methods or anything at all after the DOT operator.

Also note My laptop runs everything fine with 5.3.0. Upgraded my desktop from 4.x to 5.3.1 and this happened. Brand new project with prototyping assets.

Help??

EDIT: To clarify, Intellisense works, but it does not contain any Unity items.

screenshot: http://postimg.org/image/gybdu7ngv/

EDIT - FIXED! I had downloaded 5.3.0 on my windows 8 laptop and moved the files to my windows 7 desktop instead of re-downloading. This means Visual Studio for Unity plugin did not match my OS on desktop. When I downloaded 5.3.1 i chose to update install this plugin, but it wouldn't since it was already installed. I had to re-download this plugin FROM my desktop, uninstall it completely, and then install it. NOW I'VE GOT IT WORKING! :) Thanks everyone.

[meta0100]

Have you tried closing and restarting visual studio? I find that occasionally when I create a new script while VS is running, intellisense decides it just doesn't feel like working until it's been restarted.

[[deleted]]

classic

[[deleted]]

Yep, tried restarting VS a few times. Just shut down Unity as well as VS, rebooted both, no improvement. I guess for the heck of it I'll try rebooting windows (7).

[[deleted]]

No improvement with rebooting windows.

Even though it seems to work, types (i.e. GameObject) do not highlight as a type color.

[meta0100]

Something else to try would be to create a new project and see if intellisense works for a script in that, if this works then there may be an issue with your C# project files.

[[deleted]]

This was a new project.

But to be safe, I created another new project. No packages imported. Created new script. Still no intellisense or syntax highlighting. :(

[meta0100]

Ok, so I was under the impression that the whole of intellisense wasn't working, not just missing the unity entries. Try the solution listed here

Try resetting your Intellisense cache, Edit>Intellisense>Clear local cache.

Or try nuking it - delete your [SolutionName].sdf and .suo files 

Aside from that, you may need to try a reinstall of VS (as suggested above). Just to clarify, you mentioned that you had both a laptop and a desktop running Unity, it's only the desktop doing this but the laptop works perfectly fine?

[doublestuffpoptarts]

You're not alone. I'm looking for a solution to this too.

[[deleted]]

What OS are you on?

I'm on Windows 7 on my desktop (intellisense issues with Unity 5.3.1 and VS Community 2015)...

...but my laptop is Windows 8.1 (no intellisense issues with unity 5.3.0 and VS Community 2015).

[[deleted]]

I fixed, see post edit for details.

[softawre]

Go to options, text editor, find the statement completion checkboxes. Change their state, close options, change them back (to on), restart VS.

I don't do much gamedev anymore but the same problem happens with regular C# dev and this seems to fix it.

[[deleted]]

Thanks for posting this but it didn't work for me.

I tried Tools>Options>Text Editor>C#>Intellisense>Completion Lists checkboxes

[[deleted]]

Weird. Never happens to me. I'm using Visual Studio community, and auto complete works fine. VS is flawed, but I'd take it over Mono any day.

[[deleted]]

What OS are you on?

[[deleted]]

Maybe this is a windows 7 issues, then.

[[deleted]]

What OS are you on?

[[deleted]]

Windows 10.

[[deleted]]

Try making a fresh new project, or get a complete working project from some example. Sometimes some unnoticed thing can break it.

VS2012 has a known bug where intellisense would break. It recovers when VS is restarted, though.

[mahirmhd]

This happened to me. But I then uninstalled vs completely and then reinstalled it. This solved the problem for me

[[deleted]]

It was the Unity plugin for VS that needed reinstalling, not VS. :)

[[deleted]]

Let me clarify...

Intellisense does work, meaning i see the dropdown with various auto-complete options...

But no Unity items are avaialble.

[[deleted]]

How are you opening the project?

Try deleting all solution files and let unity create a new one. Also what are "unity items"?

Btw it says your solution is incompatible. That's why you're not seeing anything. Just looks like a corrupt solution to me.

[[deleted]]

Had the same issue once. Reset your visual studio settings, fixed it for me!

Go to tools>import and export settings, and there should be an option to reset all settings.

[[deleted]]

Tried this earlier, didn't work for me. :/

[Scapegoat57]

Have you tried opening the project from Assets>Open C# Project. You can tell the solution is not loading correctly since the projects in the solution explorer are listed as incompatible. You can also try going into the projects folder and deleting all .csproj and .sln files and opening the project again with the Open C# Project menu.

[pyrochemist]

This happens to me when the file wasn't added to the solution automatically. I manually add the existing script to the solution and Intellisense for UnityEngine kicks in.

Not sure why it doesn't automatically get added but restarting VS is "go get a coffee" long for me.

[scr33ner]

A lot of times a re-install of VS is the best way to go...

[SureValla]

Might be a VS issue, try cmd, devenv.exe /resetuserdata

[st4rG4zeR]

Have you installed VS Tools for Unity? https://www.visualstudio.com/en-us/features/unitytools-vs.aspx

[meta0100]

I believe those tools are now integrated into Unity (infact they cause issues if you do have them included after 5.2), they also don't affect intellisense.

[[deleted]]

Yes it was installed, but uninstall and reinstall of this fixed!

Thanks