Where we can, we do try to get NCrunch giving useful error messages.
In this particular case, the error was coming from a nuget package - not from NCrunch. The only way for us to improve on this error would be to introduce special handling for just this Nuget package. Given that there are a lot of Nuget packages out there, you can probably understand our limitations. If it hits this forum a lot, then we may end up doing just that.