Fsharp: No IntelliSense after re-opening multi-project solution on VS reload

[cartermp]

If you create a solution where one project references another, close VS, then re-open that solution, you will not get IntelliSense in VS 2017 RTW.

Repro steps

1. Create a new Class Library with the following (template) code:

namespace Library1

type Class1() = 
    member this.X = "F#"

1. Create a new Console App with the following:

open Library1

[<EntryPoint>]
let main argv = 
    Class1().X |> ignore
    0 // return an integer exit code

1. Close VS.
2. Open VS with the solution you just created.

Expected behavior

IntelliSense and type colorization all works, as before.

Actual behavior

No IntelliSense, type colorization, etc.

Known workarounds

Modify the project file, causing projects to reload. IntelliSense shows up again.

Related information

This may be fixed in the latest nightly, but I'm not positive until I can get that build on my machine.

[vasily-kirichenko]

Another repro: open any file in FsharpProject project in vft solution - nothing works. Go to project settings dialog, change (wrong) project type from console app to library - everything works.

[majocha]

For me the result on RTW is

but on master everything works fine.

[vasily-kirichenko]

Why file bugs found in RTW at all? It's tremendously outdated.

[cartermp]

@vasily-kirichenko People provide feedback through VS, which eventually turns into a TFS bug that finds its way to us. Any way we can convert that to GitHub, point people towards it, and verify with a larger audience, the better. It also helps in tracking what issues are (or were), and for which release.

[cartermp]

Confirmed that this is fixed in the latest nightly. Yay!

[fierval]

Issue is back in 15.1, latest nightly: 15.4.1.17040601. Workaround works.

[kaftand]

Issue is back in 15.1, latest nightly: 15.4.1.17040601. Workaround works.

Has this since been resolved? I am experiencing the same issue now (Version 15.9.8)

[cartermp]

@kaftand This was fixed a long time ago. Can you file a new issue with a repro please?

[kaftand]

I appreciate your quick response. It turns out the issue was a stupid mistake on my part :/ apologies for wasting your time.

[cartermp]

No worries!