Back to Questions
5.8k
views14
comments
How to get F# fully installed in VS2010 beta 2
f#

This is probably an RTFM question, but I seem not to be able to install F# with VS2010 b2 x86 (I downloaded the Ultimate edition - could that be a problem?) In the setup application, there is a checkbox "F#", that I have checked. There are no sub-options to that one, so I assumed that should get in installed fully.

So far, I could not not find no fsyacc.exe, fslex.exe, not a single *.fs file on the drive. My project conversion fails because "C:\Program Files\MSBuild\FSharp\1.0\FSharp.PowerPack.Targets" is not found, and such a file is not installed indeed anywhere.

I have:

"C:\Program Files\Microsoft F#\v4.0", with subdirectories "Silverlight" and "4.0". The latter contains:

1
2
3
4
5
6
7

Fsc.exe
FSharp.Build.dll
FSharp.Compiler.dll
FSharp.Compiler.Interactive.Settings.dll
Fsi.exe
Fsi.exe.config
Microsoft.FSharp.targets

and that is all I got.

Should I install a different edition of VS2010? Additional package? I am completely lost.

.

Yes, if you have F# checked, you get everything F# that ships in VS2010.

FsLex/FsYacc are part of the F# PowerPack. To get the PowerPack, install the CTP atop your VS2010 installation.

I don't recall what we have for project conversion, but if you have old projects, I presume that changing the <Import> line to point at the right directory that contains Microsoft.FSharp.targets, and setting the right ToolsVersion will work. You might create a new .fsproj file and then compare the newly created one to an old one you have.

By on 11/1/2009 9:56 PM ()

To get the PowerPack, install the CTP atop your VS2010 installation.

Will the PowerPack from the latest CTP (Oct 2009) play nicely with .NET 4.0?

By on 1/8/2010 2:50 PM ()

Yes.

By on 1/8/2010 3:12 PM ()

I have been running VS2010 beta2 on Windows Server 2008. Life was good until I tried to convert an F# solutions that uses FSYacc/FSLex.

Some idiot (that would be me) took the advice to "to get the PowerPack, install the CTP atop your VS2010 installation" a little too literally -- I copied the files in the October 2009 CTP bin directory into

Program Files(x86)\Microsoft F#\v4.0\

and overwrote the dlls already there.

When I tried to build (with Target Framework set to .Net Framework 4) BUild Output was as follows:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

c:\Program Files (x86)\Microsoft F#\v4.0\fsc.exe -o:obj\Debug\Parser.dll -g --debug:full --noframework --define:DEBUG --define:TRACE --optimize- --tailcalls- -r:"C:\Program Files (x86)\Microsoft F#\v4.0\FSharp.PowerPack.dll" -r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\mscorlib.dll" -r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Core.dll" -r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.dll" --target:library --warn:3 --warnaserror:76 --vserrors --fullpaths --flaterrors --nowarn:62 Ast.fs Parser.fs Lexer.fs fileio.fs 

FSC: warning FS0082: Resolved file has a bad image, no metadata, or is otherwise inaccessible. Could not load file or assembly 'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Core.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. (Code=MSB3246)

FSC: warning FS0082: Resolved file has a bad image, no metadata, or is otherwise inaccessible. Could not load file or assembly 'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\mscorlib.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. (Code=MSB3246)

FSC: warning FS0082: Resolved file has a bad image, no metadata, or is otherwise inaccessible. Could not load file or assembly 'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. (Code=MSB3246)

FSC: error FS0084: Assembly reference 'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\mscorlib.dll' was not found or is invalid

FSC: error FS0084: Assembly reference 'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\mscorlib.dll' was not found or is invalid

FSC: error FS0084: Assembly reference 'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Core.dll' was not found or is invalid

FSC: error FS0084: Assembly reference 'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.dll' was not found or is invalid

FSC: error FS0219: The referenced or default base CLI library 'mscorlib' is binary-incompatible with the referenced F# core library 'C:\Program Files (x86)\Microsoft F#\v4.0\FSharp.Core.dll'. Consider recompiling the library or making an explicit reference to a version of this library that matches the CLI version you are using.

FSC: error FS0229: Error opening binary file 'C:\Program Files (x86)\Microsoft F#\v4.0\FSharp.Core.dll': Exception of type 'Microsoft.FSharp.Compiler.ErrorLogger+ReportedError' was thrown.

Done building project "Parser.fsproj" -- FAILED.

Setting Target Framework to .Net Framework 3.5" allows the project to build and run fine, but I'd like to target .Net Framework 4.

Is this a simple matter of getting the F# DLLs from a 2010 beta 2 install, and restoring them to their rightful place, or have I well and truly hosed myself?

David

By on 12/16/2009 1:55 PM ()

I think this may be recoverable. In Control Panel's Add/Remove Programs, you may be able to 'repair' the install of VS2010 or the F# redistributable. I don't know the exact set of steps, but I imagine it's only a few mouse clicks and a lot of waiting.

Alternatively, (the 'simple matter' you suggest) if you have another machine to 'copy' the files that should be in that directory over (e.g. commit the same sin again in order to try to restore things), I bet that would mostly work too (though it may leave you in worse shape when it comes time to uninstall Beta2, I am not sure).

By on 12/16/2009 2:08 PM ()

> 'repair' the install of VS2010

This did the trick. After repairing the install and running the CTP msi, everything works again.

Thanks much

David

By on 12/16/2009 7:02 PM ()

Okay, thanks, Brian.

I have two followup q's:

1. What is the right way to install CTP POwerPack on top of VS2010 beta 2? Is it to run the msi, or to unzip the files to another location, say, "Program Files(x86)\FSharp-1.9.7.8", and add a reference to the PowerPack dll in that directory l (leaving everything else pointed at the VS2010 beta2 files)?

2. Does anyone have a copy of the original 2010 beta 2 F# files that they can let me have?

1
2
3
4
5
6
7

Fsc.exe
FSharp.Build.dll
FSharp.Compiler.dll
FSharp.Compiler.Interactive.Settings.dll
Fsi.exe
Fsi.exe.config
Microsoft.FSharp.targets

thanks again

David

By on 12/16/2009 2:19 PM ()

1. Just run the MSI.

2. x64 versus x86 may matter (I forget), so make sure you get files for the same machine architecture. (and failing that, try the 'repair' option)

By on 12/16/2009 2:25 PM ()

Thank you Brian, that resolved it.

I have a few other problems though. First of all, is there only one October CTP package? Maybe I have just installed a wrong one?

First problem was that .fsy and .fsl files refused to compile because msbuid was looking for files in a wrong directory. Standalone msbuild gave an error:

1

C:\Program Files\MSBuild\FSharp\1.0\FSharp.PowerPack.Targets(62,3): error MSB 6004: The specified task executable location "C:\Windows\Microsoft.NET\Framework\v4.0.21006\fsyacc.exe" is invalid.

and in VS the error was same, only the path where the executable were looked was different: "C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE"

I was able to resolve that by adding two property definitions to FSharp.Powerpack.Targets:

1
2
3

    <FsPowerPackBinPath>C:\Program Files\FSharp-1.9.7.8\bin</FsPowerPackBinPath>
    <FsLexToolPath>$(FsPowerPackBinPath)</FsLexToolPath>
    <FsYaccToolPath>$(FsPowerPackBinPath)</FsYaccToolPath>

but I am not really sure this is a kosher fix. After that, the compiled files give me warninigs, as if fslex and fsyacc produce files that are not completely syntactically compliant:

1
2
3

C:\Aigo\libFParse\stimYacc.fs(2,1): warning FS0222: Files in libraries or multiple-file applications should begin with a namespace or module declaration, e.g. 'namespace SomeNamespace.SubNamespace' or 'module SomeNamespace.SomeModule'. This will be required in a future version of F#.

C:\Aigo\libFParse\stimLex.fsl(2,1): warning FS0222: Files in libraries or multiple-file applications should begin with a namespace or module declaration, e.g. 'namespace SomeNamespace.SubNamespace' or 'module SomeNamespace.SomeModule'. This will be required in a future version of F#.

If I add a namespace directive between %{ and %} in an .fsy file, it still does not go the first line into a compiled .fs file, and that produces an error this time, not a warning.

I feel like I have a wrong package installed?

By on 11/2/2009 5:18 PM ()

So now that 1.9.9.9 of the power pack is out these are now errors. What is the fix for this?

E:\source\Lex.fsl(2,1): error FS0222: Files in libraries or multiple-file applications must begin with a namespace or module declaration, e.g. 'namespace SomeNamespace.SubNamespace' or 'module SomeNamespace.SomeModule'

E:\source\Yacc.fs(1,1): error FS0222: Files in libraries or multiple-file applications must begin with a namespace or module declaration, e.g. 'namespace SomeNamespace.SubNamespace' or 'module SomeNamespace.SomeModule'

By on 2/17/2010 8:23 PM ()

So now that 1.9.9.9 of the power pack is out these are now errors. What is the fix for this? E:\source\Lex.fsl(2,1): error FS0222: Files in libraries or multiple-file applications must begin with a namespace or module declaration, e.g. 'namespace SomeNamespace.SubNamespace' or 'module SomeNamespace.SomeModule' E:\source\Yacc.fs(1,1): error FS0222: Files in libraries or multiple-file applications must begin with a namespace or module declaration, e.g. 'namespace SomeNamespace.SubNamespace' or 'module SomeNamespace.SomeModule'

Let's continue this at

[link:cs.hubfs.net]

(thread has better title).

By on 2/17/2010 9:16 PM ()

RE: E:\source\Yacc.fs(1,1): error FS0222: Files in libraries or multiple-file applications must begin with a namespace or module declaration, e.g. 'namespace SomeNamespace.SubNamespace' or 'module SomeNamespace.SomeModule'

For the error from the fsyacc file, see also:

[link:cs.hubfs.net]

By on 5/26/2010 11:42 AM ()

No, you have the right thing installed, now you're just experiencing the fact that the lex/yacc portions of the powerpack are filled with minor bugs. :)

You've good workarounds for the ToolPath issues, and you should just ignore the warnings or add a #nowarn in the %{ %} to turn that one off.

These FsLex/FsYacc bugs are known issues to us; the PowerPack just has not gotten as much attention lately as we're been trying to finish off the core VS2010 parts.

By on 11/2/2009 6:25 PM ()

Good. The warnings I'll just ignore. Thanks!

By on 11/2/2009 6:43 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