Back to Questions
2.8k
views22
comments
The F# September 2008 CTP is now available!
f#

The new F# CTP was released earlier today. You can get all the details on Don's blog post announcing the CTP release.

Download the F# CTP

More information about the release, and links to other F# downloads are available on the new F# Developer Center at [link:msdn.com].

.

Has Mono support in the form of the p10 binaries been removed? I've tried to get it (minimally) working under OSX, certainly fsc.exe and fsi.exe are not doing me any favours with the latest mono installed. It would certainly be nice if someone in the F# team made it easy again for the rest of us. Thanks!

By on 9/4/2008 1:40 AM ()

Are you using Mono 2.0 Preview? That was the primary configuration used to test the F# CTP, including on OSX

By on 9/4/2008 4:47 AM ()

Looking great.

One small remark (for now ;) )

Is it correct that the single case active pattern (|Lazy|) got removed? If so, pretty please can you bring that back? It is simple to write, but it really cleans up code using lazy values, so it's something I would have to write over and over again.

bye

Kurt

By on 8/31/2008 6:06 AM ()

Hi Kurt,

Good suggestion, thanks. This was previously hidden away in what we now regard as a non-standard PowerPack location (the Lazy module). Like KeyValue it would make a candidate pervasive active pattern. Will record a suggestion for this.

For those missing it the definition is

let (|Lazy|) (x:Lazy<_>) = x.Force()

don

By on 8/31/2008 9:49 AM ()

Units & Measures? Quotation compilation? MSBuild?

you're really spoiling us!

Unfortunately I've run into some difficulties with the CTP. Initially I got an error

--no-framework unrecognized argument to fsc.exe.

Uninstalling VSLab fixed this. I also uninstalled all versions of FSharp, rebooted and reinstalled v1.9.6.0.

Now on running an empty F# Application project I get:

------ Build started: Project: ConsoleApplication1, Configuration: Debug Any CPU ------

C:\Program Files\FSharp-1.9.6.0\\bin\fsc.exe -o obj\Debug\ConsoleApplication1.exe -g --noframework --define DEBUG --define TRACE -r "C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Core.dll" -r C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.dll --target exe --warn 3 --warnaserror 76 --vserrors --fullpaths Program.fs

C:\Program Files\MSBuild\FSharp\1.0\Microsoft.FSharp.Targets(77,3): error MSB4018: The "Fsc" task failed unexpectedly.[EDIT: to remove superfluous stack trace and build output.]

Thinking this may be to do with the temporary location of the generated project I attempted to save the solution into my user profile documents folder, but that cause a error dialog saying 'This operation cannot be completed.'

I finally attempted to run VS2008 'as Administrator', but there was no change in behaviour.

I'm running VS2008 on a Vista Ultimate Tablet PC.

Any help much appreciated.

regards,

Danny

By on 8/31/2008 6:52 AM ()

Danny, FYI, the error you got trying to "Save As..." a project file is a known bug in the CTP release. So you might try creating the project again in a non-temporary location to see if it fixes the 'file not found' issue.

By on 8/31/2008 4:47 PM ()

Hi Brian,

Just thought I'd let you know of the setting used to disable the temporary location of new projects that gets around the 'This operation cannot be completed' error dialog when saving new projects.

Tools -> Options -> Projects and Solutions -> General -> Save new projects when created

has to be checked in order to get the project to save. I had unchecked mine to get rid of the ConsoleApplication223 problem.

regards,
Danny

By on 9/4/2008 11:06 AM ()

Don - you were quite correct here.

It seems VSLab does not uninstall fully. In particular it leaves a registry entry that overrides any call to fsc.exe with a call to the vslab wrapper executable.

To fix your system simply remove the following key from the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\fsc.exe

Please be VERY careful when editing the registry. It fixed my system - but no guarantees!

Brian - I believe I'm now in a position to install the CTP and will report back on the Project saving issue.

regards,

Danny

By on 9/1/2008 1:13 PM ()

Danny, the new version of VSLab has removed that hack! .vslab files have become .fsx files and everything has become less intrusive.

By on 9/7/2008 3:56 PM ()

Hi Danny et al

Using VS 2008.
I installed CTP without uninstalling 1.9.4.17...
VS ran but CTP seemed a bit odd (maybe it was launching VSLab and 1.9.4.17?), thought maybe I needed to convert fsprojs ...
(forget exact now but maybe VSLab keep launching every time I did anything...)
Anyway I uninstalled 1.9.4.17, and then it really went down hill (excuse my technical language)

Read some posts and tried to uninstall VSLab. It would not uninstall, becos it could not find 1.9.4.17

Now CTP launchs and when I build (VSLabs respones, still wants 1.9.4.17) I get this error... (not ready to edit registry yet, I'll wait see if the VSLab folks gen a workaround or there is some other approach thought up)

System.IO.FileNotFoundException was unhandled
Message: Could not load file or assembly 'FSharp.Core, Version=1.9.4.17, Culture=neutral, PublicKeyToken=a19089b1c74d0809' or one of its dependencies. The system cannot find the file specified.

By on 9/4/2008 10:54 AM ()

Hi Art,

I think removing the registry key

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\fsc.exe

is your only option until VSLab is updated for 1.9.6.0.

best of luck,

Danny

By on 9/4/2008 11:30 AM ()

The update of VSLab for 1.9.6.0 is proving though because of the new F# project inifrastructure. Viewlets does not depend on it but the toolbar does so I'm talking with F# team to see the best option for this new release. However it will be soon released the new VSLab where several hacks will be finally removed (like the fsc one) making me happy :)

-- Ciao

-- Antonio

By on 9/6/2008 2:57 AM ()

Danny thanks for the luck... the surgery seems to be a success, HAL VISTA VS2008 sans VSLab issue HKEY removed... 1.9.6.0 fsc.exe OK. Not singing Daisy.

By on 9/5/2008 3:57 PM ()

I have noticed two problems, just playing with it.

First, when I open properties of the project, I get a value was not within the given range.

Second, when I have more than one file in the project, and use [<EntryPoint>], I can't built.
Removing [<EntryPoint>], I can built. Funny thing here, if your building without the entrypoint, it's the file lowest in the project overview that's executed.

Oh, the new VS projects have made my busy porting my #r code. Will post about this.

By on 9/1/2008 3:56 PM ()

These are by design. Take a look at section 12.1 of [link:research.microsoft.com]

e.g.

<quote> <H3><A name=_Toc207785751></A><A name=_Toc207705984></A><A name=_Toc194259398></A><i>12.1.4 Explicit “Main” Entry Point<i></H3> <i>The last file specified in the compilation order for a .EXE may additionally contain an explicit entry point, indicated by annotating a function in a module with EntryPointAttribute.<i> <i>Ø The attribute can be applied only to a let-bound function in a module. It may not be a member. <i> <i>Ø Only one function may be given this attribute, and this must be the last declaration in the last file processed on the command line. The function may be in a nested module.<i> <i>Ø The function is asserted to have type “string[] -> int” prior to being checked. If this assertion fails an error is reported.<i> <i>Ø At runtime the arguments passed on startup are an array containing the same as entries as System.Environment.GetCommandLineArgs(), minus the first entry in that array. <i> <i>The function becomes the entry point to the program. It immediately forces the static initializer for the file in which the function exists. It will then run the body of the function.<i></quote>

By on 9/1/2008 4:04 PM ()

Never mind - files genereted by the lexer and paser will ofcourse require -r FSharp.PowerPack.dll when compiling.

By on 9/1/2008 5:00 PM ()

Hi Danny

This does still vaguely feel like a problem from having had VSLab installed, since it does some funky things.

Any chance you could try on a computer that hasn't had VSLab installed?

I know Antonio (VSLab owner) will be loking into this more soon

don

By on 8/31/2008 9:53 AM ()

I installed the CTP, however the FSI interactive windo doesnt display correctly. any text I type in is displayed as white on black. however when I press enter it is set to white on white, or grey or white on grey - no too sure what the background color is. Can some one tell me how to alter the color scheme used to display text in fsi interactive.

P.S. I am using a custom color scheme found at this link [link:blog.wekeroad.com]

By on 8/31/2008 11:20 AM ()

I installed the CTP, however the FSI interactive windo doesnt display correctly. any text I type in is displayed as white on black. however when I press enter it is set to white on white, or grey or white on grey - no too sure what the background color is. Can some one tell me how to alter the color scheme used to display text in fsi interactive.

P.S. I am using a custom color scheme found at this link [link:blog.wekeroad.com]

I had that problem too, you can solve it by editing the fonts and colors option in visual studio, in the "Text Editor" item "Read-Only Region"

By on 8/31/2008 11:48 AM ()

thanks for the help, I can not properly use FSI in VS 2k8. However, what settings other than Read-Only Region control how text is displayed in VSI. in particular I am looking to get red displayed for errors and may be a few different colors for different things.

By on 8/31/2008 2:18 PM ()

Awesome, but where's the project converter? I can't find it.

By on 8/29/2008 5:23 PM ()

A tad late, but I've posted the .fsharpp to .fsproj project converter on my blog at:

[link:blogs.msdn.com]

Cheers!

By on 8/30/2008 10:30 PM ()

    Topic tags

    IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
    Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy     		Built with WebSharper