I'd like to understand better whether we should recommend
(a) should application writers take a dependency on this package?
(b) should library writers pushing packages containing .NET 4.x DLLs to nuget specify this as a dependency?
(c) should library writers pushing packages containing PCL DLLs to nuget specify this as a dependency?
If we recommended (b) and (c) it would be very nice to adjust the ProjectScaffold to use the package, and also to mention how to set up Nuget and/or Paket to "do the right thing".
I'm somewhat convinced that the benefit of referencing the package for libraries like Deedle, FsLab and other packages is greater than the problems that it might cause.
The guidance here is pretty cautious about recommending the FSharp.Core nuget package.
I'd like to understand better whether we should recommend
(a) should application writers take a dependency on this package?
(b) should library writers pushing packages containing .NET 4.x DLLs to nuget specify this as a dependency?
(c) should library writers pushing packages containing PCL DLLs to nuget specify this as a dependency?
If we recommended (b) and (c) it would be very nice to adjust the ProjectScaffold to use the package, and also to mention how to set up Nuget and/or Paket to "do the right thing".
I'm somewhat convinced that the benefit of referencing the package for libraries like Deedle, FsLab and other packages is greater than the problems that it might cause.