Skip to content

How do I migrate to NuGet from Paket?

Note that the minimal template uses NuGet by default. This recipe only applies to the full template.

Paket is a fully featured package manager that acts as an alternative to the NuGet package manager commonly used in .NET.

It can help you reference libraries from NuGet, Git repositories or Http resources. It also provides precise control over your dependencies, separating direct and transitive references and capturing the exact configuration with each commit. You can find out more at the Paket website.

For most use cases, we would recommend sticking with Paket. If, however, you are in a position where you wish to remove it and revert back to the NuGet package manager, you can easily do so with the following steps.

1. Remove Paket targets import from .fsproj files

In every project's .fsproj file you will find the following line. Remove it and save.

<Import Project="..\..\.paket\Paket.Restore.targets" />

2. Remove paket.dependencies

You will find this file at the root of your solution. Remove it from your solution if included and then delete it.

3. Add project dependencies via NuGet

Each project directory will contain a paket.references file. This lists all the NuGet packages that the project requires.

Inside a new ItemGroup in the project's .fsproj file you will need to add an entry for each of these packages.

  <PackageReference Include="Azure.Core" Version="1.24" />
  <PackageReference Include="AnotherPackage" Version="2.0.1" />
  <!--...add entry for each package in the references file...-->

You can find the version of each package in the paket.lock file at the root of the solution. The version number is contained in brackets next to the name of the package at the first level of indentation. For example, in this case Azure.Core is version 1.24:

Azure.Core (1.24)
    Microsoft.Bcl.AsyncInterfaces (>= 1.1.1)
    System.Diagnostics.DiagnosticSource (>= 4.6)
    System.Memory.Data (>= 1.0.2)
    System.Numerics.Vectors (>= 4.5)
    System.Text.Encodings.Web (>= 4.7.2)
    System.Text.Json (>= 4.7.2)
    System.Threading.Tasks.Extensions (>= 4.5.4)

4. Remove remaining paket files

Once you have added all of your dependencies to the relevant .fsproj files, you can remove the folowing files and folders from your solution.

Files: * paket.lock * paket.dependencies * all of the paket.references files

Folders: * .paket * paket-files

5. Remove paket tool

If you open .config/dotnet-tools.json you will find an entry for paket. Remove it.

Alternatively, run

dotnet tool uninstall paket
at the root of your solution.