You are not logged in.

#1 2018-11-18 00:37:42

Jeraldson
Member
Registered: 2018-09-18
Posts: 3

Newest update to dotnet (2.1.6+500-1) causing issues with omnisharp

So I've been developing with C# and the dotnet package using vscode. I had no issues for the first few days I had things setup, but mysteriously after the most recent update (2.1.6+500-1) the C# extension for vscode started having issues. Specifically, omnisharp was failing to locate the installed sdk.

I looked through the package changelog and discovered the newest update introduced a script which is put into /usr/bin rather than symlinking the dotnet executable as was previously done. The script is very simple, just setting the DOTNET_ROOT environment variable then calling the dotnet executable itself. For a reason I still don't understand, this script is the source of my issues. I tried removing the script and putting the symlink back in, then it magically started to work again. I've compared the omnisharp log before and after the fix and there is no difference except up to the point where the error is thrown.

Having the DOTNET_ROOT environment variable set isn't the cause, since I tried manually with it set and unset and it continued to work. I have no real idea what the cause of this is. It doesn't seem to be something upstream, as it's strictly related to the existence of that script. I'm not sure if this is something warranting a bug report, or if it's just something I have to deal with. Hopefully someone else knows more.

Thanks for the help.

Offline

Board footer

Powered by FluxBB