Desmond File

Blog archive

What's New in F#?

Visual Studio 2010 and .NET Framework 4, released in April, brought a number of critical changes to mainstream managed languages like C# and Visual Basic. But the latest version of Microsoft's integrated development environment and managed framework also shifted the playing field for dynamic and functional languages, like F# and IronRuby.

We posed three questions to Mark Hoban, Microsoft senior program manager for F#. Here's what he had to say:

Visual Studio Magazine: How significant an update is the version of F# appearing with Visual Studio 2010? What key features or capabilities should developers be looking for in the new version?

Mark Hoban: Visual Studio 2010 includes the F# 2.0 version of the F# language. This is a major release of the F# language, and includes important new features and brings F# to its first supported release.

Key features of this release include simple and succinct functional syntax, rich .NET Framework object-oriented programming model, integrated parallel and asynchronous programming features, units of measure and the F# Interactive. (Details on these features can be found here.) Note that this same version of the F# language will also continue to be made available in CTP form for developers using Visual Studio 2008.

VSM: Why is F# not being fully integrated into .NET Framework 4? What must developers do to enable the F# core libraries and compiler?

MH: We view F# as a true first class member of Visual Studio and the .NET Framework, but due to the development process we are releasing this version as an additional runtime that customers will need to install on the target machines. We will review that with our next release.

VSM: Who is Microsoft looking to serve with the F# language? Has the original scope of F# expanded over time?

MH: F# extends the .NET Framework by offering a productive language for developers working in technical, algorithmic, parallel and data-rich areas. This has included applications in domains such as financial services, data analytics, games, sciences and machine learning. This is largely the same audience we’ve historically targeted with F#, though the scope has expanded slightly in response to the breadth of adoption we’ve seen over the last 2 years.

Posted by Michael Desmond on 06/14/2010


comments powered by Disqus

Featured

  • VS Code 1.123 Adds Agent Session Sync, 1M Context Windows

    Microsoft released Visual Studio Code 1.123 on June 3, adding agent-focused features, larger model context support, integrated browser updates and a new delay for some automatic extension updates.

  • Copilot Billing Shock Hits Developers

    Developer complaints about GitHub Copilot's new usage-based billing model have centered on unexpectedly rapid AI credit consumption, and neither GitHub nor Microsoft has responded directly to the backlash, though they have previously published guidance to lessen model usage costs.

  • Hands On with GitHub Copilot App Technical Preview: Turning a Blazor Issue into a PR

    GitHub's brand-new Copilot desktop app, in technical preview, handled a small Blazor issue from planning through pull request creation, but the hands-on test also showed why developers still need to verify agent work in the running app before merging.

  • At Build 2026, Microsoft Sets Up Windows as an OS for AI Agents

    Microsoft's Build 2026 Windows developer announcements point to a broader platform strategy for agentic AI, spanning terminal workflows, local models, app-building skills, Cloud PCs and operating system-level containment.

Subscribe on YouTube