News

Visual Studio 2017 v15.7 Brings F# Up to Par with C#

Though it has been around for 13 years now, F# has in some ways seemed to be the neglected little brother of the older C# language in the .NET ecosystem. During Microsoft's Build developer conference last year, for example, the company even felt the need to present a session titled "Why You Should Use F#."

The main reason you might want to use the open source, cross-platform language (stewarded by the F# Software Foundation) is for functional programming. And at this year's Build conference, Microsoft introduced new features coming with the new Visual Studio 2017 version 15.7 that bring it more up to par with the older (by five years) C#.

"Starting with version 15.7 of Visual Studio 2017, F# officially supports creating ASP.NET Core projects via the same UI that C# supports," Microsoft said in a blog post yesterday. "Additionally, all tooling for Docker, CI/CD with Visual Studio Team Services, and publishing to Azure App Service is supported."

Addressing the growing functional programming movement, Microsoft last fall announced F# support for .NET Core and .NET Standard projects in Visual Studio, and earlier released its language documentation as open source. Earlier this year it detailed updates to the language and F# tooling in VS 2017 v 15.6.

That latter vein was furthered in v15.7, with:

"We made many improvements to F# and its tools," Microsoft said in its release notes. "Performance and cleaning up existing experiences with .NET SDK-style projects has been the focus for this release. As always, we also received significant contributions from the wonderful F# community."

In yesterday's blog post, the company's Phillip Carter highlighted the performance and responsiveness improvements that were helped by the community and the Microsoft Mobile Tools team, which also helps support F# in Xamarin and Visual Studio for Mac.

These include: reduction in data structure sizes; moving metadata into virtual memory, adding a priority to document diagnostic analyzers; and more.

"Overall, the 15.7 release of Visual Studio 2017 represents one of the largest performance improvements to F# tooling in Visual Studio in a long time," Carter concluded. "We are very excited about this because it is the number one issue people have when they use F# for large solutions. We're looking forward to spending more time on tooling performance in the next year, and doing so not only for Visual Studio, but in the F# Compiler and F# Compiler Service so that all F# tooling in any editor can benefit."

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • VS Code 1.125 Adds Copilot Spend Meter After Billing Shock

    VS Code 1.125 adds in-editor visibility into additional Copilot budget usage as GitHub's AI-credit billing model continues to draw developer scrutiny.

  • TypeScript 7.0 RC Moves Microsoft's Go Rewrite Into the Mainline Compiler

    Microsoft's Go-based TypeScript rewrite has reached Release Candidate status, moving from a separate native-preview package into the regular TypeScript npm package while leaving some ecosystem-facing API work for TypeScript 7.1 or later.

  • Microsoft Highlights Visual Studio Live! Event Lineup and Longtime Developer Community Role

    A Microsoft MVP Blog post on Visual Studio Live!'s longevity arrives as the 2026 conference series continues with upcoming stops at Microsoft HQ, San Diego and Orlando.

  • Using Local AI to Cut Copilot Usage-Based Billing Shock

    After being gobsmacked by the new billing plan using almost all my monthly credits in one or two days, I tried pushing some Copilot-style coding work onto local models in VS Code. What I found was less "free AI" and more "pick your pain": cloud charges on one side, heavy local resource use and long waits on the other.

Subscribe on YouTube