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

Missing Unity types for auto-completion #449

Open
garciaErick opened this issue Aug 22, 2018 · 9 comments
Open

Missing Unity types for auto-completion #449

garciaErick opened this issue Aug 22, 2018 · 9 comments

Comments

@garciaErick
Copy link

I installed mono-develop, omnisharp on windows wsl, I installed omnisharp-server using package-install from emacs. Everything from refractoring, go-to definitions and autocomplete works for standard libraries, however none of the Unity autocompletion works. I found that in my omnisharp server there are no Unity.dll's how can I configure my omnisharp to work with my Unity projects?

@razzmatazz
Copy link
Contributor

razzmatazz commented Aug 23, 2018

@garciaErick Not sure if discovery/autocompletion on unity types would work in any way differently from a regular referenced dll/assembly. Are you referencing Unity.dll from your csproj?

Also, have you tried inspecting the *omnisharp-log* buffer? Not sure if that is helpful in your case but there may be clues..

@garciaErick
Copy link
Author

garciaErick commented Aug 27, 2018 via email

@Henry-T
Copy link

Henry-T commented Aug 28, 2018

Unity's dll is no difference to other normal dlls. Auto completion works fine for me on:

  • Emacs modified for windows
  • sln & csproj generate for Visual Studio by Unity3D

You can try VS project.

@garciaErick
Copy link
Author

garciaErick commented Aug 28, 2018 via email

@garciaErick
Copy link
Author

:(

@ar1a
Copy link

ar1a commented Dec 8, 2019

was there anything more on this? i'm running into something extremely similar on nixos

@R0flcopt3r
Copy link

I have finally gotten this working!

I got a load of conflicting packages on the next step, solution was to purge all of mono from from my system. In fedora this would be:

dnf remove mono\*

Add your relevant repository: https://www.mono-project.com/download/stable/
Install mono-complete. *omnisharp-log* will now output a bunch of msbuild information, and it all should work.

@razzmatazz
Copy link
Contributor

Just a FYI, we're going to slowly deprecate omnisharp-emacs in favor of lsp-mode / eglot. If possible, you may want to try out those two alternatives. A couple of things are still missing (like integrated unit testing runner functionality and go-to-definition for classes on compiled assemblies) but this is the plan.

@R0flcopt3r
Copy link

Nice to know, I prefer using lsp-mode, but it's having other issues, OmniSharp/omnisharp-roslyn#1898 (comment)

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

5 participants