Missing Unity types for auto-completion

[garciaErick]

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]

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

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 < ***@***.***> 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 <#449 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ad-nFI1mNPJmEvn9YjNUbmvCEsfQSXfDks5uTlZ1gaJpZM4WGzMN> .

[Henry-T]

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]

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 ***@***.***> 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 <#449 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ad-nFIWqftb-kMQrck3F_8k-xZObUA53ks5uVQq0gaJpZM4WGzMN> .

[garciaErick]

:(

[ar1a]

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

[R0flcopt3r]

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]

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]

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