Update to FCS 1.4.2.0

[dsyme]

No description provided.

[dsyme]

This exposed a bug in the newly released FCS 1.4.1: fsharp/fsharp-compiler-docs#447

[vasily-kirichenko]

Updated to 1.4.2. Waiting for CI.

[dsyme]

I have been using the Visual F# Power Tools from the CI build of this PR for two hours now (on the large FSharp.Compiler.Service project).

It feels like things have really improved - memory is still largish (as expected) but I got a lot of work done staying in the 1.3GB-1.6GB range. The UI was very responsive the whole time and all the VFPT features felt smoother. I even started to turn VFPT features back on and was able to run with unused namespace gray-out for the second session.

It honestly feels like my machine Is back alive again - I can now work on my large F# solutions with Visual F# Power Tools enabled and get all the productivity benefits that come from that.

I'd say this is ready to go in. If people want to try this on their own large solutions, here it is: https://ci.appveyor.com/project/dungpa/visualfsharppowertools/build/2.2.0-a1510161958/artifacts

[vasily-kirichenko]

@dsyme Fantastic! I cannot believe you fixed the memory issue.

[vasily-kirichenko]

@dsyme I tried to set keepAssemblyContents = false and it behaved even better. Is it worth to set this flag or there are some hidden cost behind it? I turn the flag on in this PR #1179

[dsyme]

That should default to false: https://github.com/fsharp/FSharp.Compiler.Service/blob/03e3d0260fdd670999b338b8f2cd8df8b1411899/src/fsharp/vs/service.fs#L3048

You need to set this if you want the typed expression tree (AssemblyContents) - and yes, it will use more memory.