Packs all paket.template files within this repository.
1: 2: 3: 4: 5:
1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23: 24: 25: 26: 27: 28: 29: 30: 31: 32: 33: 34:
If you add the
-v flag, then Paket will run in verbose mode and show detailed information.
--log-file [FileName] you can trace the logged information into a file.
Consider the following
paket.dependencies file in your project's root:
1: 2: 3: 4:
And one of your projects having a
paket.references file like this:
Now, when you run
paket install, your
paket.lock file would look like this:
1: 2: 3: 4: 5: 6:
Now, when you are done programming and wish to create a NuGet-Package of your project, create a
paket.template file with
type project and run:
Or, you could run:
Depending on which command you issue, Paket creates different version requirements of the packages you depend on in the resulting
.nuspec file of your package:
|Dependency||Default||With locked dependencies|
As you see here, the first command (without the
lock-dependencies parameter) creates version requirements as specified in your
paket.dependencies file. The second command takes the currently resolved versions from your
paket.lock file and "locks" them to these specific versions.
Visual Studio can be configured to download symbol/source versions of installed packages from a symbol server, allowing the developer to use the debugger to step into the source (see SymbolSource).
These symbol/source packages are the same as the regular packages, but contain the source files (under
src) and PDBs alongside the DLLs.
Paket can build these symbol/source packages, in addition to the regular packages, using the
Paket automatically replaces inter-project dependencies with NuGet dependencies if the dependency has it's own
In addition to this the switch
include-referenced-projects instructs Paket to add project output to the package for inter-project dependencies that don't have a paket.template file.
- It recursively iterates referenced projects and adds their project output to the package
- When combined with the symbols switch, it will also include the source code of the referenced projects. Also recursively.
- Any projects that are encountered in this search that have their own project template are ignored.
By default Paket uses the specified version ranges from the
paket.dependencies file as version ranges for dependencies of the new NuGet package.
by using the
minimum-from-lock-file parameter the dependencies of the generated NuGet will use the versions from the
When using a
type project any localized satellite dlls are included in the created packages.
The following layout is created:
Full name: Microsoft.FSharp.Core.Operators.not
val single : value:'T -> single (requires member op_Explicit)
Full name: Microsoft.FSharp.Core.ExtraTopLevelOperators.single
type single = System.Single
Full name: Microsoft.FSharp.Core.single
Full name: Microsoft.FSharp.Core.Operators.id
Full name: Microsoft.FSharp.Core.Operators.lock
Full name: Microsoft.FSharp.Core.option<_>
Full name: Microsoft.FSharp.Core.Operators.using
Full name: Microsoft.FSharp.Core.Operators.log
Full name: Microsoft.FSharp.Collections.list<_>