-
Notifications
You must be signed in to change notification settings - Fork 168
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
Method Not Found: GetFileName #803
Comments
This is a server issue. There's a PR for a fix in place here: OmniSharp/omnisharp-roslyn#2443 |
I installed omnisharp-roslyn v1.39.2-beta.10 (using a modified omnisharp-manager.sh) and I'm still getting the same errors. I'll do a little more digging and post in the omnisharp-roslyn project. But it looks like the latest beta doesn't fix this. |
I tried a few things to resolve this after the above. I updated Visual Studio 2022 which did not resolve the issue. Then I ran :OmniSharpInstall from gVim in Windows instead of WSL and it started working. I'm a little surprised OmniSharp in WSL knew to use the Windows install since WSL installed to omnisharp-rosly and Windows to omnisharp-roslyn. Looking at logs in ~/vimfiles/plugged/omnisharp-vim/log/ there's some obvious differences in what is being referenced. When working it's referencing .Net Core SDK, and when broken it's referencing Visual Studio. Also surprising is the Windows version change from 6.2.9200.0 to 10.0.19044.0. Not sure what that version means but I did not upgrade Windows. LOL. Broken Log
Working Log
|
It's hard to be sure from the details you've given but it looks like the "broken" version is using the older. NET Framework build of OmniSharp-roslyn, and the "working" version is using the new net6 build. |
I did add |
I get the following error for all project files when using omnisharp-vim.
I tried adding
let g:OmniSharp_server_use_net6 = 1
as resolved this similar issue, but it had no effect. Though I wouldn't be surprise if I missed some additional steps needed for WSL.These two issues from other projects seem like they might be related.
uno issue 9297
docfx issue 8097
WSL 1
dotnet 6.0.400
omnisharp-roslyn 1.39.1
Logs
full log file
The text was updated successfully, but these errors were encountered: