Skip to content
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

Cannot jump to Microsoft packages by using coc-definition #18

Open
lubyrex opened this issue Apr 17, 2020 · 3 comments
Open

Cannot jump to Microsoft packages by using coc-definition #18

lubyrex opened this issue Apr 17, 2020 · 3 comments

Comments

@lubyrex
Copy link

lubyrex commented Apr 17, 2020

I'm following the asp dotnet tutorial here:
https://docs.microsoft.com/en-us/aspnet/core/tutorials/first-web-api?
And it creates this simple file: Program.cs, which looks like this right now:
image
Doing a hover on the UseStartup method gives a definition in a floating window:
image
However using coc-definition returns "Definition not found"
Whereas in VSCode, it would jump to the Metadata file:
image
Is there a way to set up coc-omnisharp to have it exhibit the behavior in VScode?

@b93rn
Copy link

b93rn commented May 17, 2020

Same issue here. Basically the last feature i need to be able to use this in production, since i can't view internal packages.

@howin98
Copy link

howin98 commented Jan 5, 2021

so, what is the solution?

@lubyrex
Copy link
Author

lubyrex commented Jan 8, 2021

@howin98 you could use https://github.com/OmniSharp/omnisharp-vim, and map your go to definition hotkey to :OmniSharpGotoDefinition<CR> while using coc-omnisharp for your other hotkeys.

My config looks like this:
autocmd FileType cs nnoremap <buffer> gd :OmniSharpGotoDefinition<CR>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants