-
Notifications
You must be signed in to change notification settings - Fork 11
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
Is it ready yet? #5
Comments
@mikeTWC1984 it'll need at least a |
I've got |
On my end neither csproj or solution works. So was just checking if the project is still in the early stage. I tested it only on dotnet core on linux, probably it works better on Windows |
Yeah I have been unable also to get it working. No errors but incorrect suggestions. This is the only missing piece for me to abandon all other completion plugins completely in favour of coc so excited about this plugin |
could you guys provide the result of |
can repro on my side (
Omnisharp on Linux should run with Edit: figured out -- that's irrelevant, and is because I've installed mono to the system. |
Updating to omnisharp 1.34.1 did not help. |
possibly related: |
hmmmmm -- out of curiosity I tried setting project type to |
Here's my I noticed it could not find |
Tried changing "TargetFramework" property to
|
@mvrozanti yeah |
Can you share your |
I also noticed that calling |
@mvrozanti just created from the bare metal |
I would love to see this fixed. Basically this is what's keeping me 1/2 of the time in VSCode. Rest of the time (for JS/TS/..) I'm in coc.nvim. Is there any workaround? BTW, net46 as a target would not be an acceptable solution. .NET Core is wher it's at (e.g. ASP.NET Core.) |
FWIW, playing with it a little, I got to this:
This ring any bells? Edit: Looks like a bunch of |
@muratg a quick compare of
|
updated to |
well it happens to work "by chance": The target framework is @muratg in the success run, there's no error messages like you posted. |
kept trying to restart |
exceptions in the run:
|
in the following run, it doesn't work from the beginning. no exceptions in this run. failures:
|
next run, tried to edit the file before lsp initializes.
|
next run: success. note, the failure are present even in a successful run:
so perhaps they are irrelevant. |
in the following run, captured another kind of exception:
|
@yatli Thanks for the investigation! To replicate your case (make it work even for a little bit "by chance"), I created a new Console app. Now I'm getting the following whenever I try to do a code complete:
|
Would it make sense to add a command to restart OmniSharp? Kinda like tsserver does. |
Interesting, I used omnisharp-vim plugin sometime ago, and it worked with mono and solution file, but now it gives me same 2000ms error |
@muratg try |
Just tried it, still no luck. All I get from code completion is random garbage. |
the timeout constraint can be relaxed in |
Looks like there is a dependency on coc-utils extension. After installing it omnisharp is working, at least on my end (ubuntu/.net core) |
Thanks @mikeTWC1984. Unfortunately, did not work for me. Same thing as before (timeout). Also Ubuntu (18.04) and .NET Core 2.x. Do you remember installing anything else, by any chance? edit: @yatli If you have some time, could you try to see if installing edit2: Just saw that @yatli had a bunch of check-ins, so I uninstalled and reinstalled coc-omnisharp, still without success. |
Do you have vim-polyglot plugin installed? Also did you enable omnisharp extension (like when you do CocList extension, do you see * or + in before omnisharp). I also have mono installed, it was needed for original omnisharp |
Thanks @mikeTWC1984! Yep, coc-omnisharp is enabled (* next to it). Installed vim-polyglot, but didn't change anything. Mono seems to make it work better (I wasn't expecting this, because VSCode's version of OmniSharp works without Mono, I assume it uses .NET Core.) So I get completions now, but I still get timeouts each time. Also, I don't see the method signature below (like I see when I use TSServer.) Not sure if this is by-design. Also, I don't see diagnostics either. (if a line is wrong, it doesn't tell me.) |
I don't see signatures neither in vim or vscode (I would love to though), probably this might be configured. I don't see timeout errors. I'm using nvim 0.4. |
Although there is still some issues with error highlighting - it's highlighting correct lines, and not highlighting obvious errors |
👍 Yeah, I may have high expectations after experiencing TSServer. It's basically on par with VSCode. Hopefully this will get there some day too! (BTW, in VSCode, ctrl-space pops up a window showing signatures for me.) |
The |
btw if you haven't configured the notification panel, it could appear that the extension is not working, while it's downloading the server. |
@yatli Yep, after seeing your commits, I uninstalled and reinstalled coc-omnisharp -- still didn't work. Adding Mono made it work better (I get completions fine now.) Though still get timeouts even if it works. Not sure why the dependency on Mono is, though. VSCode uses omnisharp too (AFAIK) and it works fine without Mono on the machine. So currently my problems are:
|
@muratg unfortunately I also notice that linting is absent for the latest release of |
@yatli I think you're right. Mono is probably a red herring. (Because it didn't work after I typed that comment! Now it semi-works again.) So all 3 issues above stay issues for me. |
A bit of explanation of non-parity with VSCode: In the vscode extension, it connects to the omnisharp server with a custom protocol (not lsp), and there's a lot of code between O# and VSCode, serving as middleware and enhancing the functionalities here and there. The language server feature of O# started much later in the development, and recently has undergone huge refactoring to leverage So currently we've got two options, one is to wait for upstream O# lsp improvements, and the other is to start porting the vscode extension middlewares over. The latter would require a lot more work, and would only be possible if we can team up to do it. edit: the latter option is actually practiced and proven to work -- see |
@yatli Thanks a lot for the details, I didn't know VSCode/OmniSharp connection was still custom! Makes sense now. I like both options, but former appears to be more realistic at this point. BTW, are you still getting timeouts as well? |
Thanks for this work. So I guess now it is better to use https://github.com/OmniSharp/Omnisharp-vim as it has more features (like go to definition, enhanced syntax highlighting, refactoring, other). 😞 C# development on VIM is a frustration to setup environment. Coc.nvim is really great but it seems MS does not want to contribute to plugins (deoplete, coc.nvim, other) and pushes its plugin (O#-vim). |
I believe some of the problems listed here (especially the sync/invalid completion list at point) were resolved with: Not released yet, though. I have also added support for (to be merged by maintainers):
|
Whoa, thank you @razzmatazz , these PRs are super cool! |
I can confirm auto-completion works good out of the box now. It also able to discover class files as you add them.
|
Should be mostly ready now... :) |
Just started to play around. At a glance it doesn't seem to work properly. I see some suggestion from LS, but mainly snippets/key words. I don't see any methods/properties, or stuff from added packages. Example:
Does it need mono and solution file (like original omnisharp?)
I'm on linux, using core sdk 2.2, nvim 0.37
The text was updated successfully, but these errors were encountered: