Get started by learning how to use Paket and take a look at the FAQ to learn more about it. If you are using legacy NuGet (packages.config -based) projects for package management in your solution, …

The install.sh script will add Paket as a command line option into bash and most other shells available. If you are using a unique shell and run into problems, please post an issue so we can take a look.

Paket manages your dependencies with three core file types: paket.dependencies, where you specify your dependencies and their versions for your entire codebase.

If you're not using .NET Core, or you're stuck on .NET Core 2.2 or lower, you can use the paket bootstrapper. Create a .paket directory in the root of your solution.

Paket will then go through your solution and convert all new NuGet projects to Paket. Paket stores paket.dependencies and paket.lock files in the root of a repository.

Paket provides support for .NET SDK -based projects that are used with the dotnet CLI (running with .NET Core) or with MSBuild 15 (Visual Studio 2017 and Mono 5).

Paket uses this definition to compute a concrete dependency resolution, which also includes transitive dependencies. The resulting dependency graph is then persisted to the paket.lock file.

After converting your solution from NuGet, you may end up with many transitive dependencies in your Paket files. Consider using paket simplify to remove unnecessary transitive dependencies from your …

Using Paket from F# Interactive F# Interactive integration Editor support Shell completion Credential Providers API Reference Paket commands paket add paket auto-restore paket clear-cache paket …

Paket allows you to automatically manage the linking of files from github.com or gist.github.com into your projects. If you have Git installed then Paket also allows you to reference files from other git …