One thing I neglegted to mention was that there isn’t really out of the box editor support for targeting both
netstandard1.6 (or higher versions).
My standard workaround for this have been to only target netstandard1.6 or lower for most of the relevant assemblies that I work on a day to day basis on. This works for most of the internal libraries since we deploy either
netcoreapp2.0 to Azure.
For libraries that are supposed to be consumed by a wider set that has been a bit of a pain to edit on Mac OS X.
If you try to open a .net core project that uses paket, the workaround to edit projects in Visual Studio for Mac is to disable automatic package restore.
The final workaround to be able to work
netstandard1.6 dotnet core project on Mac OS X is to apply @enricosada’s fix to
export FrameworkPathOverride=$(dirname $(which mono))/../lib/mono/4.5/
Do you want to send a comment or give me a hint about any issues with a blog post: Open up an issue on GitHub.
Do you want to fix an error or add a comment published on the blog? You can do a fork of this post and do a pull request on github.