Fake dotnetcore

Getting Started

Getting started with the Fake dotnetcore version is easy. Just install the corresponding package for your system:

choco install fake -pre

now you can use

fake --help

This is basically it. You can now execute fake commands.

For unix we don't have packages jet (please contribute!), but you can use the manual install process (see Contributing)


See Fake command line

Buildserver support

AppVeyor: https://github.com/fsharp/FAKE/blob/master/appveyor.yml Travis: https://github.com/fsharp/FAKE/blob/master/.travis.yml


The goals are:

  • Provide a easy to use cross platform way to use FAKE. With a good bootstrapping experience
  • Cleanup 'FakeLib'
  • Extract reusable libraries and make them usable for your projects or the fsi!
  • Make it easier to extend FAKE for your own use-case
  • Provide an easy way for simple scripting, automate everything, everywhere.

Please read https://github.com/fsharp/FAKE/issues/1232

What is the migration path?

See Fake 5 Migration Guide

How to specify dependencies?

See the FAKE 5 modules section.

Portable installation

We distrubute a dotnetcore version of FAKE without the dotnetcore runtime. This version assumes an existing dotnet sdk installation while the non-portable installation doesn't.

Just use the -portable version of the downloads, extract it and execute.

dotnet Fake.dll <regular-arguments>

The advantage of this method is that it is portable (ie. distribute the same binaries) and requires less bandwidth. The disadvantage is that you need to have a dotnet sdk installed.


  • See https://github.com/fsharp/FAKE/blob/master/build.fsx Note that with the "new" API you should call the modules directly instead of opening them. Therefore this example is actually pretty bad because it just opened everything (for minimal diff to the "normal" build.fsx)



Get the latest alpha packages from GitHub: https://github.com/fsharp/FAKE/releases