Error loading fsx: "internal error: BuildFrameworkTcImports: no successful import..." about fsautocomplete HOT 3 CLOSED

It was suggested that perhaps optdata and sigdata were required to be deployed along side FSharp.Core?

from fsautocomplete.

Thanks for the report. I think that this is actually a problem with FSharp.Compiler.Service, which does not actually support F# 4 yet as far as I know. The strange behaviour that you see is because FCS then falls back to looking for FSharp.Core in the current directory, and find one without the .sigdata or .optdata, which it will always have in the GAC. This is related to #12

There is some guidance on the sigdata and optdata here: http://fsharp.github.io/FSharp.Compiler.Service/corelib.html

I don't believe that we want it so necessarily end up using FSharp.Core 4.3.0.0 if there isn't one found, as this might mask other errors. This is the reason I haven't included .optdata, .sigdata so far. However, I'm not 100% sure. In your situation if they were present, then you would have FSAC type-checking your scripts against FSharp.Core 4.3.0.0 while VS is type-checking them against FSharp.Core 4.4.0.0 which can't be a good thing.

One resolution to this problem would be for me to look for the returned references and strip out any reference to the FSharp.Core bundled with FSAC, which should then end up being a sensible error (could not find FSharp.Core).

from fsautocomplete.

Fixed by #59

from fsautocomplete.