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

C# extension cannot start omnisharp on Linux due to wrong casing of 'omnisharp' executable #152

Closed
gregg-miskelly opened this issue Apr 6, 2016 · 3 comments · Fixed by #153
Assignees
Labels
Milestone

Comments

@gregg-miskelly
Copy link
Contributor

  1. Install daily build of .NET CLI
  2. Install the 1.0.0-rc2 build of the C# extension

Result:
[INFO] Starting OmniSharp at '/home/greggm/clicon'...
[ERROR] Error: Could not fnd launch file in /home/greggm/.vscode-alpha/extensions/ms-vscode.csharp-1.0.0-rc2/.omnisharp. Expected 'run', 'omnisharp', 'omnisharp'

Expected:
Omnisharp starts

This is from:

omnisharp-vscode\src\omnisharpPath.ts(14):const omnisharpExeFileName = process.platform === 'win32' ? 'omnisharp.exe' : 'omnisharp';
omnisharp-vscode\src\omnisharpPath.ts(41):        throw new Error(`Could not fnd launch file in ${filePathOrFolder}. Expected '${runFileName}', '${omnisharpFileName}', '${omnisharpExeFileName}'`);

The issue is that the file casing is wrong.

@DustinCampbell DustinCampbell added this to the 1.0.0-rc2 milestone Apr 6, 2016
@DustinCampbell DustinCampbell self-assigned this Apr 6, 2016
@DustinCampbell
Copy link
Member

@MattGertz -- because Linux has a case-sensitive file system, the C# extension fails to start the OmniSharp server. It works on Windows and OS X perfectly, but fails on Linux. Does this meet the bar for escrow?

@MattGertz
Copy link

Yes, I would definitely take this to Escrow. I'll send a note to TPTB.

@DustinCampbell
Copy link
Member

OK. I just sent you an email that you can use to start the conversation.

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

Successfully merging a pull request may close this issue.

3 participants