Unable to open System.Private.CoreLib.sln in Mac with "not support framework" error message

[tinytinymelon]

Environment Information:

OS : Mac OS 10.13.6
Visual Studio : Visual Studio for Mac Community version 7.6.8 (build 38)
.Net SDK : dotnet-sdk-2.1.402-osx-x64
Coreclr code : Master branch with latest commit as: 6f66b1e

Actions

1. browser into folder : coreclr/src/System.Private.CoreLib
2. click "System.Private.CoreLib.sln" to launch the Visual Studio
3. Visual Studio complains and shows error message

Error Message

Error while trying to load the project '/Users/leoninez/projects/coreclr/src/System.Private.CoreLib/System.Private.CoreLib.csproj': Project does not support framework '.NETPortable,Version=v4.5'

Need help

1. I wonder if I installed the wrong sdk or anything I missed? Please help me.
2. The VS in Mac seems only use mono as .net runtime. Could use CoreCLR built from source code as the .net runtime?

Thank you very much

[kaby76]

I don't know if you solved this problem, but I had a similar problem just on Windows. I could not find any instructions on how to open the .sln file in VS 2017 IDE from a straight clone from the Git repository. Reading the build scripts, a solution that works requires two steps: (a) do a "./build" of the code in Coreclr. This is required to generate files. (b) set PYTHON to the full path of the Python executable, which you can check with "command -v python from within Bash". This is because the .csproj uses $(PYTHON). With that, I can open the .sln file, do critical navigation, evaluation, and changes of the code for my port of System.Private.CoreLib. Building within the IDE doesn't work, but ./build does so NBD.

[dotnet-policy-service]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

[dotnet-policy-service]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.