Skip to content
This repository has been archived by the owner on Jan 8, 2019. It is now read-only.

FAQ

Jump to bottom
Enrico Sada edited this page Jun 20, 2016 · 13 revisions

Some FAQ, info about development for .NET Core. Some apply only to F#, others to all languages.

If something works with C# should works exactly the same for F#.

TABLE OF CONTENTS

  • This is a FAQ, real docs?
  • .NET Core works with F#? Now? Without going crazy?
  • Preview? RC?
  • How can i install it?
  • I maintain an F# library published as nupkg and i want to support .NET Core
    • Ok i want to start to convert a project?
    • a new target framework?
    • what dependencies version of libraries/tools?
    • how can i check version resolved?
    • some code need to be changed for .net core.. two version!
    • Can i create a single nuget package with multiple framework versions inside (.NET 4.6, .NET Core)?
      • But i already create the nuget package in my build, i dont want to use project.json for every framework
        • i need to merge nupkg manually?
  • Tools support?
  • Travis/Appveyor

This is a FAQ, real docs?

The docs https://dotnet.github.io/docs/getting-started/index.html are really nice to read, and explain all scenarios.

So it's a really good first read.

It's also open source docs, send a pr 😄

.NET Core works with F#? Now? Without going crazy?

Yes, from beta was already ok with workarounds ( ref https://github.com/enricosada/fsharp-dotnet-cli-samples/wiki/Changelog#v1.0.0-beta-002071 )

Now with preview1 work OOTB, see for example a suave sample app, working cross platform (win/ubuntu/osx/docket).

It's a not RTM, if you see bugs, open an issue in:

Preview? RC?

When .NET Core was in beta, the tooling (dotnet/cli, project.json, xproj) and the .NET Core (coreclr, corefx, bcl) was bundled together using same version (beta and after rc2).

The dotnet team split the two parts, the .NET Core (more ready for production, RC quality => RC2) from tooling (renamed from .NET CLI to .NET Core SDK, now in preview1)

So:

  • .NET Core (RC2) => Run apps with .NET Core runtime, clr and base class libraries, (dotnet/coreclr, dotnet/corefx)
  • .NET Core SDK (preview1) => tooling. Develop apps with .NET Core and the SDK+CLI (Software Development Kit/Command Line Interface) tools, like dotnet/cli (the tool who run dotnet build)

How can i install it?

See the docs https://dotnet.github.io/docs/getting-started/installing/index.html

  1. From http://dot.net choose .NET Core.
  2. That page show the quickstart. For F# add --lang f# to dotnet new.

Or Follow the (a bit hidden) Other downloads for other os and types.

Both .NET Core and .NET SDK has two versions:

  • from os native installers: like msi/pkg, install globally in the machine (see options)
  • from binaries: just a zip, download => unzip => add to PATH => dotnet ready (multiple version can be installed in different directories). Zero fear about breaking the machine configuration.

I maintain an F# library published as nupkg and i want to support .NET Core

Ok i want to start to convert a project?

There is not an updated tutorial yet ( the https://github.com/enricosada/fsharp-dotnet-cli-samples/wiki/Migrate-fsproj-To-.NET-CLI works for beta, but procedure is the same )

procedure usually is

  1. go to same directory of you .fsproj
  2. dotnet new --lang f#
  3. If it's a library, change the dependency to from Microsoft.NETCore.App to NETStandard.Library inside project.json (see below)
  4. If a library, remove emitEntryPoint attribute in project.json
  5. fix versions of deps (see below) and of compile-fsc tool.
  6. check it build ( dotnet restore followed by dotnet build )
  7. add all source files, same list as Compile inside .fsproj
  8. add all additional nuget packages dependencies, like in .fsproj
  9. add all compiler directive in buildOptions.defines of project.json
  10. do dotnet build and fix errors
  11. do dotnet pack to create the package

Check some alredy converted projects, like https://github.com/SuaveIO/suave

a new target framework?

See docs, it's explained better https://dotnet.github.io/docs/core-concepts/packages.html

Usually, simplified (again read the docs)

Type Name TFM Latest version as preview1
library .NET Standard netstandard netstandard1.5
console app .NET Core Application netcoreapp netcoreapp1.0

TFM mean target framework moniker, the short name ( ref nugets targetframeworks docs )

So, simplified:

  • a library should target netstandard1.5
  • a console app should target netcoreapp1.0

what dependencies version of libraries/tools?

Usually is ok to check files generated by dotnet new --lang f# but preview1 has some little mistake, so read about Notes for F# in .NET-Core-SDK-preview1.

A F# library should depends (inside dependencies) on:

  • Microsoft.FSharp.Core.netcore: contains the FSharp.Core assembly, no GAC in .NET Core, only nuget packages
  • NETStandard.Library metapackage: read the docs, version depends on features
  • additional packages as needed, but not Microsoft.NETCore.App metapackage

A F# console app should depends (inside dependencies) on:

  • Microsoft.FSharp.Core.netcore: contains the FSharp.Core assembly
  • Microsoft.NETCore.App metapackage: read the docs, version is 1.0.0-rc2-3002702 for preview1

As per preview1:

Package Version Same default of dotnet new?
Microsoft.FSharp.Core.netcore 1.0.0-alpha-160509 NO, was updated ⚠️
NETStandard.Library depends but usually 1.5.0-rc2-24027 YES, but dotnet new create a console app, no library! ⚠️
Microsoft.NETCore.App 1.0.0-rc2-3002702 YES
dotnet-compile-fsc 1.0.0-preview1-* NO ⚠️

how can i check version resolved?

do dotnet restore and open project.lock.json, search for package name.

some code need to be changed for .net core.. two version!

If some code need to be changed, it's possible to maintain two version of same code under '#if` defines. When building, an upper case compiler define of TFM is passed to compiler.

so if

    "frameworks": {
        "netstandard1.5": {

a compiler directive NETSTANDARD1_5 (the . becomes _) is passed to compiler

NOTE the compiler is F# 4.0, so it's possibile to use #if !DEF, #if A || B and #if A && B

like

#if NETSTANDARD1_5
   let a = typeof<Program>.GetTypeInfo().Assembly.Name
#else
   let a = typeof<Program>.GetType().Assembly.Name
#endif

Can i create a single nuget package with multiple framework versions inside (.NET 4.6, .NET Core)?

yes, nuget packages support multiple version, and the .NET Core framework it's like another target framework (like PCL, or .NET 3.5).

just add the dependency group in nuspec file and assemblies under lib

But i already create the nuget package in my build, i dont want to use project.json for every framework

No need to go all in with project.json (it said it is not feeling well lately...)

You can use the .NET SDK cli tools (like dotnet pack or dotnet build) to build the assemblies (or the package) and add these to you package

i need to merge nupkg manually?

nuget pack expects a nuspec and directory, so works already.

NOTE BY AUTHOR the following dotnet-mergenupkg it's an option written by me (@enricosada), so i like it and use it for some F# opensource project (suave/FCS/chessie). It try to not change current build workflow, but use dotnet cli to max. Feel free to ignore it.

Or you can use a opensource third party tool (https://github.com/enricosada/dotnet-mergenupkg) to merge the already built packages.

  1. build you package A normally
  2. Create a package B with .NET Core using dotnet pack
  3. use dotnet mergenupkg to merge assembly/nuspec from B to A. so A contains both.

Tools support?

  • Visual Studio: not yet
  • Visual Studio Code: With the Ionide plugin for F#. After the first build, should work.
  • Notepad: from day 0

Travis/Appveyor

Some pr are in progress to add it to .net core documentation, so easier to see pr files and discussion:

Clone this wiki locally