-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FSharp.Formatting for F# 3.1 implicitly reading FSharp.Core 4.4.0.0 #328
Comments
My impression was that (when invoked via F# Interactive and not as a stand-alone application) F# Formatting will always load the I think this would be sensible behavior - otherwise, the values you get from |
How can I reproduce this? I have installed both F# 4.0 and F# 3.1 as well, but everything seems to be working fine for me. I agree with @tpetricek and I tested with Yaaf.FSharp.Scripting with the F# 3.1 fsi.exe and the F# 4.0 fsi.exe and it was always using the current FSharp.Core. But it is quite possible that I got something wrong in the |
I cant get fsfromatting to work either I get FSharp.Core version mismatches and also Microsoft.Build.Utilities masmatches when runing the documentation generator for FCS:
|
I have tried the standalone command line tool with the metadataformat option with pretty much the same errors. |
Same here, building on mac os x (v 10.11.1) I am getting:
But when building on Windows or on Linux, everything runs fine. So, it seems to be a mono version dependency issue? On mac os x I am running mono version 4.0.5. The build that passes on Travis uses mono 4.0.4. |
Its not a particular mono version I get the same with F# master at https://github.com/fsharp/fsharp |
I'm still not sure what's happening here. One thing I figured out recently is that when running things via FAKE, we always get the version of FSharp.Compiler.Service that comes with FAKE (and is used to invoke the script that then calls F# Formatting which then uses F.C.S.). This is a bit problematic - in practice, it means we need to keep in sync with FAKE (in some way) - though this is not really a package dependency in one or the other direction. The most recent releases are synced though, so should work, I think... But that does not answer the issues with FSharp.Core versions. |
There are really 2 use cases for FSharp.Formatting
@7sharp9 @halcwb Can you try to use the following patch (fsprojects/ProjectScaffold#217) in your build scripts and report if that fixes the issues you are seeing? Let's continue discussing on #356 as I think the initially reported bug is no longer valid (until the next F# upgrade) and sadly I could never reproduce it... |
Ill try out the projectscaffold fix although one of my problems was I could not build Fsharp.Formatting, has that now being addressed? |
Yes FSF has the same problem in its build script, will update as soon as it is sure that this in fact fixes the problem. Could you test? |
I'm using the latest FSharp.Formatting on a Windows machine with both F# 4.0 and F# 3.1 installed. I'm running from a F# 3.1 command prompt.
I'm getting an error where the FSharp.Core 4.4.0.0 (from F# 4.0) is now being used by the FSharp.Formatting toolchain (for example the error below). This is a bug - the FSharp.Formatting toolchain is currently built on FSharp.Compiler.Service for F# 3.1 and should never be reading FSharp.Core 4.4.0.0 unless explicitly directed to do so.
Has the change to Yaaf.FSharp.Scripting caused this? Or is it an implicit reference to FSharp.Core 4.4.0.0 flowing from elsewhere, e.g. FCS itself? Either way the FSharp.Formatting tooling feels somewhat broken right now, or at least not working in an isolated way,
I feel we need to move to a model where the reference set being used by interactive evaluation with FSharp.Formatting is more locked down.
cheers
don
The text was updated successfully, but these errors were encountered: