Open mhutch opened 6 years ago
/cc @mrward @nosami
The NuGetPackageInstaller could either:
3 - Might be OK. 2 - Might be better since it would show all the NuGet activity.
Seem this only happens with PackageReference, with packages.config the exception string is "Could not install package 'FSharp.Core 4.3.3'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author."
Since there is a better error message for packages.config - that makes me think that something should be improved for PackageReferences problems in general, not just when the NuGetPackageInstaller is used in tests. I think currently NuGet returns a flag saying the restore failed - maybe there is more information in the restore result we get back from NuGet that we could include in the exception being thrown.
Agreed. Logging would still be useful though :)
When
MonoDevelop.PackageManagement.Tests.Helpers.NuGetPackageInstaller
fails due to a package incompatibility error, the resulting exception is not useful:I eventually figured out I could place a tracepoint in
MonoDevelop.PackageManagement.PackageManagementEvents.OnPackageOperationMessageLogged
and tracked the problem down to a framework compatibility issue. However, it would be much much better to get useful logs from CI.