-
Notifications
You must be signed in to change notification settings - Fork 417
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
start server on mac os failed #817
Comments
It looks like OmniSharp was successful launching (no failures) but it couldn't locate reference assemblies for your project. It does this by looking for the location of mono on the system. Is Mono on your path? Could you run |
@DustinCampbell |
i face the same problem because of the sln is a unity project . |
@indie21: We support unity projects, so I don't think that would be the reason for the issue. |
@sandao, I've got a few other questions:
|
@DustinCampbell OmniSharp server started wth Mono OmniSharp: -s /Users/Sandao/Projects/Unity/AGame/AGame.sln --hostPID 9477 --stdio DotNet:enablePackageRestore=false --encoding utf-8 --loglevel debug formattingOptions:useTabs=false formattingOptions:tabSize=4 formattingOptions:indentationSize=4 |
Ah, OK. So, the problem is specifically with the Emacs verison? |
@DustinCampbell yes!I use spacemacs! |
It sounds to me like the Emacs host might not be using the latest omnisharp-roslyn? We had a problem with locating Mono on zsh awhile back but that was fixed in early February: #756. |
@DustinCampbell |
ah... yes, that should only return true if omnisharp-roslyn is actually running on Mono. If you run one of the platform-specific standalone omnisharp-roslyn builds (which run on .NET Core), the MSBuild support is somewhat limited. The .NET Core versions can only get so far with non-.NET Core MSBuild projects (like Unity) because they tend to run MSBuild tasks that are intended to run on Mono or desktop .NET Framework. Note that the Homebrew for omnisharp-roslyn has been updated to include an omnisharp-mono formula (OmniSharp/homebrew-omnisharp-roslyn#3) to make it easier to get the Mono build. We'll eventually be dropping the .NET Core standalone versions of OmniSharp in favor including an embedded version of Mono with OmniSharp so that everything can be self-contained and MSBuild will work as well as we can make it (#666). |
@DustinCampbell ok,thank you! |
@sandao @DustinCampbell omnisharp-emacs now has semi-auto server installation procedure built in and it selects the proper tarball/zip file for the platform. So there should not be any need to muck with server setup manually. I would suggest this can be closed unless @sandao still has problems with the latest version of omnisharp-emacs |
OK. I'll got ahead and close this here. @sandao, let us know if there is anymore trouble. @razzmatazz: Note that we've made several changes to the way that omnisharp-roslyn is deployed. Hopefully, this will be easier for you now. Let me know if you have any questions. |
OS X 10.12.4
OmniSharp:
The text was updated successfully, but these errors were encountered: