Phillip Carter

TL;DR We’ve moved the F# GitHub repository from microsoft/visualfsharp to dotnet/fsharp, as specified in the corresponding RFC.

F# has a somewhat strange history in its name and brand. If we roll back the clocks to the year 2015, F# sort of had two identities.

We’re excited to announce general availability of F# 4.6 and the F# tools for Visual Studio 2019! In this post, I’ll show you how to get started, explain the F# 4.6 feature set, give you an update on the F# tools for Visual Studio,

Starting with Visual Studio 2019 Preview 4, we'll be adjusting how C# versions are treated in .NET tooling. Firstly, we're adding two new Language Version (LangVersion) values: LatestMajor and Preview. Rad the post to see how they stack up with the currently supported list of values.

This post was written by Lena Hall, a Senior Cloud Developer Advocate at Microsoft.
F# Software Foundation has recently announced their new initiative — Applied F# Challenge! We encourage you to participate and send your submissions about F# on Azure through the participation form.

F# 4.6 is now fully released. See the announcement blog post for more.
We’re excited to announce that Visual Studio 2019 will ship a new version of F# when it releases: F# 4.6!
F# 4.6 is a smaller update to the F# language,

Another preview of Visual Studio 2019, another update on the cool stuff going into it!
We’re pleased to announce some updates to the .NET Core tools for Visual Studio 2019. You can try these changes out starting with Preview 2. We’d love for you to try out these new features and give us feedback.

Update! Starting with Visual Studio 2019, the option has moved to:
Tools Options Environment Preview Features
Old post for posterity:
Starting with Visual Studio 2017 version 15.9, we’ve changed how the Visual Studio tooling for .NET consumes .NET Core SDKs. Prior to this change,

Today, we’re incredibly pleased to announce general availability of F# 4.5.
This post will walk through the changes in F# 4.5 (just like the preview post), then show some updates to F# tooling, and finally talk a bit about where what we’re thinking about for the next F# version.

Accounting for this change on Windows build servers: You may be doing one of the following things to install F# on a Windows build server. Installing the full Visual Studio IDE Installing the F# Compiler SDK MSI Neither of these options have been recommended for some time, but are still available with F# 4.1. For using F# 4.5 in a Windows build server, we recommend (in order of preference), Using the .NET SDK, the FSharp.Compiler.Tools package, or the Visual Studio Build Tools SKU.
Better async stack traces Starting with F# 4.5 and FSharp.Core 4.5.0, stack traces for async computation expressions: Reported line numbers now correspond to the failing user code Non-user code is no longer emitted For example, consider the following DSL and its usage with an FSharp.Core version prior to 4.5.0: Note that both the f1 and f2 functions are called twice.

We’re excited to share updates about changes to F# and F# tools which shipped with the Visual Studio 2017 version 15.7 release. Let’s dive in!
Type Providers now support .NET Standard
For those who aren’t familiar with Type Providers, they are a feature of F# which allow you to get IntelliSense for data.