Question 1

How do I install F# on Debian Linux?

Accepted Answer

Use 'apt-get install fsharp' as provided by the downstream mono/linux-packaging-fsharp repository, but note that updates may lag behind official releases and depend on maintainer availability, as mentioned in the README.

Question 2

Can I use the latest F# compiler without Visual Studio?

Accepted Answer

Yes, by adding the FSharp.Compiler.Tools NuGet package to your project, which includes the compiler and F# Interactive for .NET Core and .NET Framework. However, you must manually edit your project file to override the in-box compiler.

Question 3

Is this fsharp/fsharp repository still active for contributions?

Accepted Answer

No, it's archival. The README states that all contributions now go to dotnet/fsharp, so this repo only serves historical packaging purposes and should not be used for new development.

Question 4

FSharp.Compiler.Tools vs official .NET SDK: which one is better?

Accepted Answer

For most projects, the official .NET SDK tools are preferred as they are actively maintained and integrated. FSharp.Compiler.Tools is archival and useful only for specific compiler override scenarios, but lacks current updates.

Question 5

How to override the F# compiler in my .NET project?

Accepted Answer

Reference the FSharp.Compiler.Tools NuGet package and manually modify your project file to point to the compiler from the package, as detailed in issue #676 linked from the README. This process is not automated.

Question 6

What's the best way to get F# on macOS for .NET Core?

Accepted Answer

For .NET Core projects, use the official .NET SDK which includes F# tooling without Mono. This repository's macOS packaging relies on Mono via BockBuild, which may not be ideal for pure .NET Core workflows.

F#

What is F#?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions