I think it is a bug since it is just very very new. CokileCeoi CokileCeoi 1, 2 2 gold badges 13 13 silver badges 26 26 bronze badges.
Make sure you're running the Code version you expect. You are running the system-wide installation of Code, while having the user-wide distribution installed as well. Note that I was also getting the following warning when opening the older version, and searching for the warning led me to instructions on removing the other version, which in turn fixed the IntelliSense problem. In Programs and Features, I removed the one that didn't have " user " at the end of the application name, and when I opened Code again, it started downloading packages, one of which was OmniSharp, and then IntelliSense started working. I was launching from the command prompt and it kept running the older version. In my case the problem was that I had 2 versions installed. You just have to pick up the language type from the bar at the bottom the button with the flame. From what I've seen, IntelliSense cannot be activated on a. OmniSharp will look in your currently opened folder for project files. In your screenshot, the left sidebar says "You have not opened a folder".
How to solve this problem? OmniSharp doesn't know where your project files are. I don't think it is bug, maybe I did something wrong when installing VSCode. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information. Subscribe to RSSĬhange your preferences any time. By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. My current situation: all existing Intellisense is working, but it's not recognising new classes I add unless I exit Visual Studio and go back in again. I got round this by removing the Microsoft.EntityFramework Nuget library (I had to also remove too, since this depended on it), then adding them both back in, making sure to include at least version 6.2 of the former (otherwise I got another runtime error to do with the FirstOrDefaultAsync method called somewhere!).
When I recompiled my solution, it gave a few CS0433 compilation errors with duplicate namespaces for the MinLength and MaxLength directives in some identity user name and password validation code. vs folder (again), which seemed to solve the problem. However, one thing to watch out for - after doing this, Visual Studio recognised my classes but no longer recognised built-in ones (all the referenced namespaces at the top of my controllers were underlined in red). I deleted the packages folder at the base level of my project (somewhat nervously, as I wasn't sure if it was needed), and thought it had solved the problem, but no such luck. I thought I've finally solved the problem by following the advice from Homer.
Unticking the Track Changes option in this menu: Tools-> Options-> Text Editor-> General.
vs folder doesn't seem to solve anything (doing so also means you lose your current window layout, as well as any bookmarks you've set)