omnisharp-emacs icon indicating copy to clipboard operation
omnisharp-emacs copied to clipboard

Missing Unity types for auto-completion

Open garciaErick opened this issue 6 years ago • 9 comments

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?

garciaErick avatar Aug 22 '18 00:08 garciaErick

@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..

razzmatazz avatar Aug 23 '18 07:08 razzmatazz

I am using the Unity.dll on my csproj, I have autocomplete on my Visual Studio... How do I reference the Unity.dll on onmisharp? I tried copying the windows Unity.dll to my omnisharp location in WSL...

Erick Garcia Graduate Research Assistant iLink @Cybershare +52 1 656 375 6477 javascript:void(0); erick-garcia.com [email protected]

Find me on:

http://github.com/garciaErick https://linkedin.com/in/garciaErickCs

On Thu, Aug 23, 2018 at 1:15 AM Saulius Menkevičius < [email protected]> wrote:

@garciaErick https://github.com/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?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OmniSharp/omnisharp-emacs/issues/449#issuecomment-415316006, or mute the thread https://github.com/notifications/unsubscribe-auth/Ad-nFI1mNPJmEvn9YjNUbmvCEsfQSXfDks5uTlZ1gaJpZM4WGzMN .

garciaErick avatar Aug 27 '18 20:08 garciaErick

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.

Henry-T avatar Aug 28 '18 09:08 Henry-T

ok I see that there is some xml in the omnisharp directory... do I need to reference the unity dll in there as well? Is there some resource I can take a look at? I am sorry for the trouble. The only thing I did is paste the Unity.dll where the rest of the .dll's are but I think there is some additional configuration to be done.

Erick Garcia Graduate Research Assistant iLink @Cybershare +52 1 656 375 6477 javascript:void(0); erick-garcia.com [email protected]

Find me on:

http://github.com/garciaErick https://linkedin.com/in/garciaErickCs

On Tue, Aug 28, 2018 at 3:17 AM Henry.T [email protected] wrote:

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.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OmniSharp/omnisharp-emacs/issues/449#issuecomment-416511983, or mute the thread https://github.com/notifications/unsubscribe-auth/Ad-nFIWqftb-kMQrck3F_8k-xZObUA53ks5uVQq0gaJpZM4WGzMN .

garciaErick avatar Aug 28 '18 16:08 garciaErick

:(

garciaErick avatar Sep 06 '18 21:09 garciaErick

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

ar1a avatar Dec 08 '19 14:12 ar1a

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.

R0flcopt3r avatar Sep 01 '20 07:09 R0flcopt3r

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.

razzmatazz avatar Sep 01 '20 07:09 razzmatazz

Nice to know, I prefer using lsp-mode, but it's having other issues, https://github.com/OmniSharp/omnisharp-roslyn/issues/1898#issuecomment-684045663

R0flcopt3r avatar Sep 01 '20 08:09 R0flcopt3r