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

Why Omnisharp Roslyn isn't .NET Core base on OSX/Linux ? #1384

Closed
xsoheilalizadeh opened this issue Jan 15, 2019 · 2 comments
Closed

Why Omnisharp Roslyn isn't .NET Core base on OSX/Linux ? #1384

xsoheilalizadeh opened this issue Jan 15, 2019 · 2 comments

Comments

@xsoheilalizadeh
Copy link

xsoheilalizadeh commented Jan 15, 2019

You said in the readme:

OmniSharp-Roslyn is built with the .NET Core SDK on Windows and Mono on OSX/Linux. It targets the net461 target framework. OmniSharp requires mono (>=5.2.0) if it is run on a platform other than Windows.

So the question is that why we don't use .NET Core for OSX/Linux platform? I think it's cloud be better and we'll have .NET Core advantages instead mono. I there any plan for this?

Also here we have an image that shows even OmniSharp for Windows is .net framework.
code---insiders_2018-10-07_22-04-04

@xsoheilalizadeh xsoheilalizadeh changed the title Why Omnisharp Roslyn isn't .NET Core base in OSX/Linux ? Why Omnisharp Roslyn isn't .NET Core base on OSX/Linux ? Jan 15, 2019
@filipw
Copy link
Member

filipw commented Jan 15, 2019

This is by design, and is needed to in order to use MSBuild tasks targeting Full Framework - as they don't work on CoreCLR. Note that OmniSharp ships with its own embedded mono runtime too, so it can run even if you don't have a global mono installed. In other words, a full framework based OmniSharp can support all kinds of projects (full framework, .net core, unity etc) but a .net core based OmniSharp has a lot of troubles supporting non-.NET Core projects. We used to build .NET Core OmniSharp in the past but we went away from it.

You can find more information here #988 and here #666 and here #915

@filipw filipw closed this as completed Jan 15, 2019
@xsoheilalizadeh
Copy link
Author

Thanks!

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

No branches or pull requests

2 participants