You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Http builds of OmniSharp do not output anything to stdout, making it very difficult to diagnose errors.
The simple way to demonstrate is to download both the stdio and http versions of any build from the latest release, extract them both, then try to run them with no flags from a directory containing a .sln. The stdio build outputs nicely, nothing from the http build.
I have tested this in arch linux, using omnisharp-linux-x64.tar.gz and omnisharp.http-linux-x64.tar.gz using the run script. I have also tested in Windows 10 using omnisharp-win-x64.zip and omnisharp.http-win-x64.zip. I have also git pulled the latest version on Windows and built it in Visual Studio and tested with bin\Debug\OmniSharp.Http.Driver\net461\OmniSharp.exe vs. bin\Debug\OmniSharp.Stdio.Driver\net461\OmniSharp.exe. All with the same outcome.
The text was updated successfully, but these errors were encountered:
The Http builds of OmniSharp do not output anything to stdout, making it very difficult to diagnose errors.
The simple way to demonstrate is to download both the stdio and http versions of any build from the latest release, extract them both, then try to run them with no flags from a directory containing a .sln. The stdio build outputs nicely, nothing from the http build.
I have tested this in arch linux, using
omnisharp-linux-x64.tar.gz
andomnisharp.http-linux-x64.tar.gz
using therun
script. I have also tested in Windows 10 usingomnisharp-win-x64.zip
andomnisharp.http-win-x64.zip
. I have alsogit pull
ed the latest version on Windows and built it in Visual Studio and tested withbin\Debug\OmniSharp.Http.Driver\net461\OmniSharp.exe
vs.bin\Debug\OmniSharp.Stdio.Driver\net461\OmniSharp.exe
. All with the same outcome.The text was updated successfully, but these errors were encountered: