Announcing the F# February 2010 Release

[ NOTE: Please uninstall any older version of F# before installing VS 2010 RC. If you don’t, you will need to uninstall everything, then reinstall ]

[ NOTE: Please uninstall Visual Studio 2010 Beta2 before installing F#  ]

I’m very pleased to announce the February 2010 release of the F# language  This release of F# is available as part of:

  •   The RC release of Visual Studio 2010

  •   The matching MSI for use with Visual Studio 2008, .NET 2.0 and Silverlight

  •   The matching ZIP of standalone compiler binaries, for use on .NET, Mono (Linux/Mac/Windows) and other CLI implementations

As expected, this is very much a stabilization release as it marks the near-final step on the road to Visual Studio 2010 RTM, with F# integrated in the Visual Studio product.

However, in one small way, this release also represents a culmination of 4 years of development of the F# language:  in this release the F# “language” version number has been incremented to 2.0.  The four years we’ve worked on F# 1.x has seen the addition of the many things that make F# special as a programming language on top of its functional programming base: objects, active patterns, sequence expressions, asynchronous computations, constructs for parallelism, many refinements to the library, F# Interactive, and huge improvements in tooling, intellisense, project system and debugging. We’re glad to be continuing these improvements with this release, and, above all, giving people the base they need to enjoy long and productive use of F#.

Today, we are also very excited to be releasing the F# Power Pack on CodePlex under the Microsoft Public License. The F# Power Pack is a set of additional tools and utilities provided by the F# team, which will grow and evolve separately from the stable core F# releases. For more information see the F# Power Pack site on codeplex.

As the focus for this release of F# has been stability, there are only minor F# language additions since the October 2009 release.  The changes are described in the detailed release notes.  In the F# library, there have also been only minor additions since the October 2009 release.  Some constructs deprecated in previous releases have now been removed.  When porting older F# code (pre-Beta2) to the newest F# release, it is highly recommended that you migrate first to the October 2009 release, so that the useful deprecation warnings are available.  When migrating from the October 2009 release, please first ensure your code is “clean” with regard to the deprecation warnings given in that release.

Thanks yet again for all the excellent feedback you’ve provided throughout the development of the F# 1.x releases. 

Comments (8)

  1. C0 says:

    F# for VS2008 always crashes when compiling.

  2. C0 says:

    I mean version for VS2008, and I also have VS2010 installed, the F# in VS2010 works.

    Hi C0 – could you send details of your installation to fsbugs AT microsoft DOT com?  We’ve had one other report of this problem and we need to get to the bottom of it. Thanks, Don


  3. honu says:

    Congrats to Don and the F#UN group!

    And thanks CO, I was just about to install …

  4. Will I need to install the latest CTP if I’m running VS2010 RC?

    This is great news, F# is really nice language to use.

  5. trdunsworth says:

    I’ve tried to d/l and install on a new Win 7 box with VS2008 sp1 installed on it and I get an error saying it needs me to install .NET 2.0 even though I have .NET 3.5 sp 1 on the box. I will send to the email address above too, but curious about what’s up

  6. Andy Le Couteur Bisson says:

    F# installer fails to install VS2008 integration.  The installer completes OK and the F# interactive runs but there is no VS integration.  Following a suggestion elsewhere I have tried running “devenv.exe /setup” but this fails with a “The operation could not be completed” dialogue.

    VS2010 beta 2 was installed but removed before f# installation.

    Cannot reinstall f# either

    Andy: could you send these details (plus details of VS version etc.) to fsbugs AT microsoft DOT com?



  7. print_endline used to be supported in 1.9.8.

    It would give a nice error message saying you had to add a reference to the FSharp.PowerPack.dll.

    Now, no error message, and that function not supported in PowerPack

     Hi Adam: Please reference FSharp.PowerPack.Compatibility.dll



  8. will says:

    Hi Don,

    I’ve just been introduced to F# and find it an awesome development tool that could dramatically increase productivity quite-a-few fold.

    However I’ve hit a major problem:

    F# can output .NET modules but cannot consume them. What’s up with that?

    We have a multi-language solution that we “link” together into a humongous dll where I would like to introduce some F# goodness but am unable to due to this restriction.

    Any possibility this could be added sometime in the future?

    Hi Will,

    Could you send problems describing your full scenario to fsbugs @”?  There may be ways to address this.