Is there any way to get Intellisense in VS 2015 Community Edition to work with Unity 5.2 on Unity objects in C#? For example Intellisense doesn’t seem to understand things like GameObject, Transform or ScrollRect.
Sounds like a bug, could you report it?
Same behavior with VS 2015 (Case 727189). I uninstalled VSTU, installed it again, created a new project and it all started working.
For previously created projects, I deleted all sln and vcx* files (to force project recreation) and those projects also started working.
2 Likes
I deleted all the sln, csproj, json files, the .vs, bin and obj folders in the root project folder and Intellisense started working. Thanks for the tip.
Had the same issues. Deleting the sln/csproj/bin/obj files didn’t seem to help, but deleting the JSON files did. (or it coulda been it took 2 tries…)
No intellisense here either. I created a new project and still nothing.
UPDATE: Uninstalling and reinstalling VSTU did the trick.
scbundy: How did you go about reinstalling VSTU? From this link? https://visualstudiogallery.msdn.microsoft.com/8d26236e-4a64-4d64-8486-7df95156aba9
Because I just tried uninstalling/reinstalling from that link and it’s still broken.
Thank You!
Looks like this issues back in Patch 5.2.0p1 
Have to close unity and vs, and delete vs files, each time it happens…
whenever I add an updated unity version, I find the first thing to do before running unity is to run a “repair” with VSTU in via control panel > programs and feature
this seems to correct any problems mentioned above for me…
Doesn’t unity 5.2 have UnityVS/VSTU built in now? I’ve removed VSTU from my project and set the editor to visual studio and it all works proper.
@tswalk i’ll try that, thanks,
@Doddler yea 5.2 integrated vstu for the unity side so no need for it in your project anymore, as far as i know the installation of vstu still adds unity integration to visual studio
just tried that out, without vstu theres no integration on the visual studio side
ya, it’s integrated, but it (meaning VSTU) still needs to be installed on the system for it all to congeal.
hopefully, just running ‘repair’ will do the trick as it also should regenerate any templates needed for visual studio…
nope,
But its only happening after I build now,
so just deleting the 2 project*.json files gets it working again after reloading the solution
Got it to work by deleting the JSON files only.
Been looking for a solution quite a time, thanks!
Having similar problems
I installed unity 5.2 which then automatically installed VS Community…can’t get intellisense to work. I deleted all vs related files as mentioned above but everything still the same
I couldn’t find was the JSON files, anyone knows where they are located?
Any other possible solution?
Edit/Update:
I also just did the repair, after repair is complete I get the following warning message:
“Please correct the following problems to ensure full product functionality
Visual Studio Tools for Unity : The specified account already exists.”
Any ideas?
Edit/Update #2: [Problem Solved]
There are two repair location (both don’t fix the problem):
1- You go to control panel->Programs->Uninstall a program->MS Visual Studio Community 2015->Change->Repair (This repair method will not fix anything and the problem persists)
2- Go to this Visual Studio’s link:
https://www.visualstudio.com/en-us/features/unitytools-vs.aspx
Click link number 3 that reads: “3 FREE VS Tools for Unity”
Run the file, it will ask you whether you want to repair or remove. Repair will not fix the problem (I tested it)
Here are the steps I took to fix the problem:
1- Run the file from the link above again (if you chose repair the first time and it didn’t work) but this time select ‘remove’ instead of repai to remove VSTU completely.
2- After the removal process finished I rebooted my computer.
3- I then went to the same link above and ran the VS Tools for Unity
4- This time it started installing VSTU.
5- After it finished installing I rebooted my computer again.
6- After computer rebooted, I opened my unity project and from Unity I clicked on one of the scripts which automatically opened VS 2015 and now intellisense was working fine
Hope this helps others
Thank you
Hi, same problems here, but none of the above solutions work for me …
Currently running Unity 5.2.1f1 with VSTU installed, I noticed yesterday that some of the words werent highlighted in VSTU and that i couldnt bring up those words in intellisense. So i tried to switch to monodevelop which appearantly had the same problem. What i found weird was that eventually only one class had working intellisense and the rest of my classes did not. But as it is now, intellisense doesnt work with any of my classes.
Things ive tried out:
- Delete the .csproj and .sln files from the project (not sure what you mean by json files, as there are none in the project folder)
- Reinstall of VSTU (I used the build in VSTU until the problem occured)
- Repair of VSTU
I also noticed that whenever i delete the csproj and sln files and then try to open my scripts in VSTU via unity, it tries to start VSTU but after a short while Monodevelop starts up instead and the VSTU loading screens just hangs. Even though that i make sure that VSTU is set as default.
Hopefully does someone got a solution, Thank you.
I just installed Unity 5.2.2 with all the options about what to install selected. It showed that Visual Studio Community 2015 and VSTU would be downloaded and installed but that didn’t happen. Neither was even downloaded. And this is on a virgin Windows 10 machine that just arrived yesterday…a completely new installation of Unity. No other software except for the drivers for various devices has been installed. What’s up with this?
I would just install VS2015 community using its’ installer as well as VSTU… they’re both free to use and download separately. Install order goes:
Unity
VS2015 community
VSTU
and I’m fairly certain the default options for VS2015 or fine.
I uninstalled Unity and reinstalled it and this time everything is OK. Maybe since that option to install Visual Studio is selected by default and the option above it isn’t, I accidentally unselected it (meaning to select it) the first time.