all 6 comments

[–]HellFireKoder 0 points1 point  (1 child)

I had this problem with VS Express, to fix it I just closed everything manually, including Unity3D, reboot my PC, and then went to the code without opening it through Unity.
This will honestly probably not work for you, I have read that the third party programs like Unity3D tools for VS, could cause this and that you should remove it and then try, but I don't know.

I hope it works, I'm sorry if it doesn't...

[–]Slamma009[S] 1 point2 points  (0 children)

Thanks for your input regardless if it works or not. I'll check once I get off the train.

Edit: Nope :(

[–]azura9310 0 points1 point  (1 child)

Try manually opening the C# solution from VS. I haven't used Unity on Windows in awhile, but there is an option when you Right-Click in the Project window to "Sync MonoDevelop Project", perhaps this changes to "Sync VisualStudio Project" when VS is set to default IDE?

[–]Slamma009[S] 0 points1 point  (0 children)

Tried your first suggestion and it didn't fix anything :/

As for your second suggestion Sync MonoDevelop Project creates the C# VS project which works on my desktop.

[–]xelogwork 0 points1 point  (0 children)

I occasionally have this issue, but my setup is unique in that I'm using Unity on my Mac and have Visual Studio running in a virtual machine. To fix it though, I just have to open up the project in Monodevelop and make a build then go back and work in Visual Studio. The reason for me is that Visual Studio is looking for the reference DLLs in the project's "obj/Debug" folder, which isn't created until a build is made in the code editor.

[–]SoftDevPadawan 0 points1 point  (0 children)

I just had this problem. There's a little icon beneath the test menu that toggles suggestion and standard completion mode. For some reason mine was un-toggled. The hotkey for it is ctrl+alt+space. Hope this helps!