Paket should warn if dependencies includes FSharp.Core without redirects.force

[CraigStuntz]

Description

New F# coders are often confused at how to properly link FSharp.Core. The official documentation can be intimidating.

Paket should warn when FSharp.Core is included in paket.dependencies without specifying redirects:force

Repro steps

Given:

source https://nuget.org/api/v2

nuget FSharp.Core

When I execute .\paket.exe install:

Expected behavior

PS MyProject> .\.paket\paket.exe install
Paket version 3.6.1.0
Skipping resolver for group Main since it is already up-to-date
MyProject\paket.lock is already up-to-date
WARNING: Fsharp.core should always specify redirects:force in paket.dependencies. For more information, please consult https://fsprojects.github.io/Paket/dependencies-file.html
4 seconds - ready.

Actual behavior

PS MyProject> .\.paket\paket.exe install
Paket version 3.6.1.0
Skipping resolver for group Main since it is already up-to-date
MyProject\paket.lock is already up-to-date
4 seconds - ready.

Known workarounds

Pull out hair, post question to Stack Overflow

[forki]

I marked this up-for.grabs. It should be easy to do.

[haf]

Are you saying it should include redirects:force for library authors, too?

[forki]

for the libs itself it doesn't really matter. but since you probably have tests in the lib project...

[ntregillus]

I am getting this exact issue with a forked project, and I still don't understand the workaround or fix for this issue on the project I forked https://github.com/ntregillus/LinqToSalesforce

[pkese]

New F# coders are often confused at how to properly link FSharp.Core. The official documentation can be intimidating.

Since this is neither fixed nor documented, it would be really nice if someone at least explained what needs to be done in order get rid of this problem.