-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C#: No symbols matching #1038
Comments
Hi -- sorry for taking so long to get to this! It looks to me like the repro steps aren't complete. At the very least, I see failures when we're loading projects that init-tools.cmd needs to be run first. Will try that. |
It looks to me like there is just such a sheer number of projects in core\fx\src that the OmniSharp server times out before it gets everything loaded. The default timeout is 60 seconds. I increased that to 600 on my machine by setting the "omnisharp.projectLoadTimeout" setting in VS Code and it finished properly. I couldn't get Ctrl+T to show anything, but I'm not surprised given the sheer size of what was thrown at it. 😄 I was able to get hover tool tips and intellisense working however. I suspect there's likely some performance work that can be done for to make symbol search work properly. However, it functioned as best as it could. |
With the latest VSCode release I noticed that after the C++ extension (using CLang) is installed, C++ symbols work. Sadly, C# still doesn't work. I'm working around this by using Sublime and its integrated parser (Ctrl+Shift+R will correctly find the symbols without the Omnisharp plugin installed). |
Closing as a lot has changed since this issue was opened. Please open a new issue if you are still having issues with symbols. |
Environment data
dotnet --info
output:VS Code version:
C# Extension version:
1.5.3
Steps to reproduce
Expected behavior
The HttpClient symbol is found in multiple files.
Actual behavior
"No symbols matching" even if the only file opened contains the type definition:
The text was updated successfully, but these errors were encountered: