Make debugging "Cannot find compilation library location for package X" easier

**Title**
Many times, and I literally mean it, many times when I've upgraded .NET Core to a higher version, I've encountered a repeating error while trying to run my applications. And that is when runtime complains that it *can't find a compilation library location for package X*.

**Description**
The problem is, we don't know how to debug this frustrating issue. We go into a blind heuristics approach, trying so many stupid things in vain.
So many threads and issues about this error has been submitted, including [this one](https://github.com/dotnet/core/issues/1725) that I've submitted almost 2 years ago.

And I can't believe that still after many hours of frustrations of development community, we don't get a clear message or guide on how to debug this.

We're all developers, and we all know how hard is it to create something robust. We know that you guys are doing your best to provide us with a valuable infrastructure and you have to deal with custom architectures, different platforms, competitive performance, hunger of new generations for new features, ever-growing technologies to support and many more topics.

But ALL I'm asking for is that you provide more information. Why it can't find that library? Where it has searched? Where it expects that library to be? I've checked and that library is in output folder and it's located in the relative path that it has to be.

If it's the error of traversal dependencies, then what dependency can't be loaded. If it's the error of conflicts, then what libraries are conflicting? Give us more information.

To be honest, I can't even understand what it means. It's like a Martian language to me. I think this sentence is not even syntactically correct.

Or at least provide some help or documentation on MSDN or anywhere so that when we google we can find it and get a little help.

When I say I'm clueless, I'm not joking. I'm a .NET developer for 14 years, and I just have no idea, not even a single clue on where to look, how to debug, what to do. Any every time it happens it hurts our business. It costs us real money, because we usually can't solve it in hours and it sometimes costs us even weeks.

Please please please do something about this error.

Thank you so much.