Paketized .NET SDK 2.0 projects using paket.references don't seem to work so well in VS for Mac

Description

I'm using paket happily on my Mac.

However I've had several occasions where I've had strange behaviour with new-style .NET SDK 2.0 paket.references projects, especially after opening the project in VS for Mac. In each case the implicitly referenced DLLs just stopped being referenced

Initially this happened visibly when building from VS for Mac. However the behaviour also persisted when I went back to the command line and used msbuild again, which makes me thing that some cached file of computed references was corrupted by VS for Mac.

If we get a reliable repro or if this sounds like another bug reported elsewhere then we can plausibly get a bug fix into VS for Mac

Workaround

Avoid using paket.references with .NET SDK 2.0-style projects that you want to be able to edit with VS for Mac

Repro steps

Exact repro steps TBD - I mainly want to know if this is a known issue yet

The issue names no files, tests, or entry points, and its exact reproduction steps are still TBD. Start by establishing a reliable reproduction involving paket.references, .NET SDK 2.0 projects, VS for Mac, and msbuild; done means documenting the reproduction and determining whether the behavior is a known issue.