The problem might be caused because of paket's default framework restrictions and your dotnet version mismatch. For example; as of date 2021-12-27 and paket version 6.2.1 when you paket init, by default in paket.dependencies file there is this line:
In C#, how to Paket Add dependencies to all projects in a folder even ...
Paket solves this by specifying which project needs a dependency ('paket.references') and which version of a dependency should be used ('paket.dependencies') separately.
As per the paket documentation adding storage: packages to your paket.dependencies file should do it.
This will generate F# scripts in ./.paket/load. There will be a load script for each dependency (and its transitive dependencies) and for each Paket "group". This can automatically sync with your paket.dependencies if you add this line:
Paket is a third-party package manager with somewhat different semantics. I reached a point in my project where I have to add packages properly (instead of just pulling them in on the CLI when testing) There is only one way that packages get added to a .NET project via NuGet, and that is by recording them in its .csproj file.
I installed paket from nuget in Nuget Package Manager Console with: Install-Package paket I then tried to run paket convert-from-nuget. It stalled out on a user prompt (it wouldn't let me type i...