Visual Studio 2017 and Unity 2018.2.7f1 not communicating?
I'm just a student so I don't know the specifics of what's going on but when I'm coding in Visual Studio 2017 I used to get autofill on Unity-related things like Game Objects. As of about a week ago this stopped. It seems like Visual Studio doesn't realise that it's linked to Unity. It's causing a few problems as now it's a lot harder to see where I've gone wrong, and I'm not sure what I did to disable this feature or how to turn it back on. I might as well be writing in notepad at this point.
Any ideas? I'm willing to provide screenshots or anything else you might need to give me a solution
Answer by Vicarian · Jan 23, 2019 at 02:43 PM
This happens a lot, especially when making new scripts from within the editor. There are a couple of ways around this. First, you can check the Solution Explorer in Visual Studio to make sure the script you're trying to work with is actually in the solution. You may use the Solution Explorer to add an existing item (being the class that VS is missing). Second, you can safely delete the Visual Studio solution files from disk and allow Unity to recreate them. They're one level up from your Assets folder. Third, you may close the solution from the File menu in VS and reopen it.