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

Update with latest OmniSharp and pick correct version for current Linux distribution #188

Merged
merged 2 commits into from
Apr 15, 2016

Conversation

DustinCampbell
Copy link
Member

We've updated OmniSharp to build releases for each Linux distribution that we currently support: CentOS, Debian, Red Hat (RHEL), and Ubuntu. This change adds code to sniff out which of the supported Linux distros we're running on to determine which flavor of OmniSharp we need to download and install.

cc @gregg-miskelly, @chuckries, @caslan, @Pilchie, @david-driscoll

…ux distribution

We've updated OmniSharp to build releases for each Linux distribution that we currently support: CentOS, Debian, Red Hat (RHEL), and Ubuntu. This change adds code to sniff out which of the supported Linux distros we're running on to determine which flavor of OmniSharp we need to download and install.
@Pilchie
Copy link
Member

Pilchie commented Apr 14, 2016

👍

@DustinCampbell
Copy link
Member Author

Note, I may rebase this against 'dev' and resubmit if we think this is important enough to reset Escrow for RC 2.

@chuckries
Copy link
Contributor

👍

1 similar comment
@gregg-miskelly
Copy link
Contributor

👍

@caslan
Copy link
Contributor

caslan commented Apr 14, 2016

LGTM

@david-driscoll
Copy link
Contributor

Should there be a default when we hit the none case? I'm thinking of other distros like Arch, this would would then make @markrendle cry if vscode broke for him.

Perhaps at that point prompt the user to select the most compatible distro? I know many are debian based, including ubuntu. Perhaps that's a good default.

@DustinCampbell
Copy link
Member Author

@david-driscoll -- good suggestion. How do others feel? Would Debian or Ubuntu be a good fallback if the user is on a different distro than one of the "blessed four"? It's likely that OmniSharp may work in those cases, and if not, OmniSharp will simply fail to start.

@gregg-miskelly
Copy link
Contributor

I don't know that the chances that it would actually work are terribly high -- coreclr is extremely picky.

Could a user download there own and set the omnisharp path? If so, that would be my recommendation.

@DustinCampbell
Copy link
Member Author

@gregg-miskelly, yes, that's how others would use it. Essentially, they could download the Mono version and be certain of having it work.

@gregg-miskelly
Copy link
Contributor

Should we spit something to the output window telling them how to do that?

@DustinCampbell
Copy link
Member Author

Possibly -- threading that through is a bit tricky because the omnisharpDownload.ts module is used by Gulp as well, which can't have a dependency on VSCode. Let me take a look.

@gregg-miskelly
Copy link
Contributor

Optional call back delegate?

@DustinCampbell
Copy link
Member Author

No, I can put this elsewhere.

…c to the current Linux distribution can't be found
@DustinCampbell
Copy link
Member Author

OK, I added a commit that provides instructions to the user if we fail to find a version of OmniSharp that targets the current Linux distribution. Thoughts?

output.appendLine("OmniSharp provides a richer C# editing experience, with features like IntelliSense and Find All References.");
output.appendLine("It is recommend that you download the version of OmniSharp that runs on Mono using the following steps:");
output.appendLine(" 1. If it's not already installed, download and install Mono (http://www.mono-project.com)");
output.appendLine(" 2. Download and untar https://github.com/OmniSharp/omnisharp-roslyn/releases/download/v1.9-alpha13/omnisharp-linux-mono.tar.gz");
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll file an issue to make this a bit more robust for RTM. We don't want to have to update this URL everytime we release.

@gregg-miskelly
Copy link
Contributor

LGTM

@dnfclas
Copy link

dnfclas commented Apr 15, 2016

Hi @DustinCampbell, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!

The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.

TTYL, DNFBOT;

@DustinCampbell
Copy link
Member Author

We have sign off from shiproom as well.

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

Successfully merging this pull request may close these issues.

7 participants