I’m happy to see a number of people blogging about F# when I search the web these days, but I haven’t seen anything posted about our concrete plans since this post five months ago which declared that
We will be partnering with Don Syme and others in Microsoft Research to fully NEW Battery for HP 500 HSTNN-IB44 HSTNN-C29C HSTNN-FB39 434045-661 integrate the F# language into Visual Studio and continue innovating and evolving F#. In my mind, F# is another first-class programming language on the CLR.
So I thought I would post a minor update regarding our plans. No dates are firm, but fujitsu fmvlbp103 battery our intention is to have a CTP release (Community Technology Preview) some time this summer. Nothing is set in stone, but the main features I think are most likely to be in the CTP are:
* Runtime components:
o fsc.exe, the compiler that knows the F# language
o fsi.exe, the interactive command environment
o the F# libraries (usual stuff, ranging from immutable lists Battery for HP/COMPAQ NX1050 NX9000 NX9005 NX901 to asynchronous computations library)
o an msbuild task which lets you build an F# “.fsproj” project from the command line
* Design-time components (Visual Studio 2008 integration):
o F# language service, which provides syntax highlighting, intellisense, tooltips, etc.
o F# project system, which enables you to add/remove .fs files, reference dlls, etc.
o F# interactive window, where fsi is hosted inside Visual Studio
This is roughly on par with what you can currently download in the F# research samsung q10 battery release. Though there will be some feature improvements, a lot of the work we have now involves driving up the product quality by fixing bugs clevo laptop battery and usability issues. (Thanks to everyone who has already given us feedback through fsbugs@microsoft.com.)
So stay tuned in to the blogs of those on the F# product team (which I linked to in a prior post) for more info about all aspects of F# and our plans for deliverables in the coming months.
Related Topics: