Open afterwind-io opened 5 years ago
For anyone encountered the same problem, I found a temporary solution.
Add omnisharp.json
in your project folder with:
{
"MsBuild": {
"MsBuildSDKsPath": "/usr/local/share/dotnet/sdk/2.2.103/Sdks",
"UseLegacySdkResolver": true
}
}
Where .../sdk/[version]/...
the version part in MsBuildSDKsPath
should point to the version you desire.
Hope it works for you.
Seems like a duplicate of #1416.
I tried updating to latest roslyn release, and use the suggestion above for omnisharp.json
. While it no longer complains about not finding the sdk, vscode complains about everything, from using System
to a simple void
.
Here I am running Linux Mint, and dotnet 2.1.602. Happy to help with the debug.
@afterwind-io it works :)
dot net update to 2.1.603, still same problem.
Today I stumble upon the same error. Installing the dotnet through the official mac installer solve the problem for me. Using SDK v3.1.4.
I am having the same issue this morning I updated to 8.10.5(build 16) dot net 5.0.7
I had the same problem, and in my project, the .sln
(and all the rest projects) are in a sub folder.
When I opened the VSCode on that sub-folder, it works.
@afterwind-io Your answer is still working but has you figured out the permanent solution for this? it may create conflict everytime code is sync on two different mac machines.
VSCode Version: 1.32.3
dotnet --info
:.csproj
:OmniSharp Log: