With SDK 3.1.401, loading .NET Core projects with some problems in VSCode.

[dandanmu]

Environment data

dotnet --info output:
.NET Core SDK (reflecting any global.json):
Version: 3.1.401
Commit: 5b6f5e5005

Runtime Environment:
OS Name: Mac OS X
OS Version: 10.15
OS Platform: Darwin
RID: osx.10.15-x64
Base Path: /usr/local/share/dotnet/sdk/3.1.401/

Host (useful for support):
Version: 3.1.7
Commit: fcfdef8d6b

.NET Core SDKs installed:
3.1.401 [/usr/local/share/dotnet/sdk]

.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.1.7 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.7 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

VS Code version:1.47.3
C# Extension version:1.22(v1.22.2)

Steps to reproduce

1.Install VSCode.
2.Launch VSCode and install the C# extension.
3.Install Mono 6.12.0.90 and “omnisharp.useGlobalMono” is set to “auto” .
4.Create a new .NET Core project.
5.Open the project in VSCode.

Expected behavior

The project succeeds to load, build and run succeeded without any problems.

Actual behavior

The project succeeds to load, build and run succeeded with some problems.

Note:
For .NET Standard projects, it loads as expected without any problems.

[filipw]

thanks, you already opened this issue before - #3935 (comment)

[JoeRobich]

@dandanmu Testing locally I see that it is resolving runtime references from NuGet instead of the dotnet SDK. If you enable the LegacySdkResolver, it will locate the references appropriately.

Creating omnisharp.json as described below, in ~/.omnisharp/ or project directory.

{
   "msbuild": {
       "UseLegacySdkResolver": true
   }
}

[georgikoemdzhiev]

@dandanmu Testing locally I see that it is resolving runtime references from NuGet instead of the dotnet SDK. If you enable the LegacySdkResolver, it will locate the references appropriately.

Creating omnisharp.json as described below, in ~/.omnisharp/ or project directory.

{
   "msbuild": {
       "UseLegacySdkResolver": true
   }
}

Thank you! That resolved the same issue for me. I use version 3.1.302

[cartermp]

Closing as duplicate of #3935

Unfortunately this one is a horrible experience and not easy to deal with :(