F# intellisense sometimes stops working

[daniel-wojcik]

I noticed that sometimes Intellisense in F# editor is not working (can't find any pattern): there are no member prompts, no syntax coloring and F12 key is also not functional. After spending some time to find the solution I came to conclusion that it is enough to delete project.assest.json file from obj project folder. After a few seconds after deleting this file all Intellisense functionality is restored.

Windows 10 21H2
VS 2022 17.2.0. Preview 2.0 and 3.0

[kerams]

I'm seeing something similar with FSharp.sln. It seems like I need to run Build.cmd every time before I open VS, otherwise the F# integration is completely dysfunctional.

[vzarytovskii]

I've checked the latest 17.2 preview as well as 17.3 from main, and don't see it anymore. I will close it for time being.

[daniel-wojcik]

@vzarytovskii I simply don't understand why this issue was closed - have you in any way verifed it? I'm constantly experiencing this problem, also on newest VS 17.2.0 Preview 6. Below two merged screenshots: upper before deleting obj/project.asset.json, lower: after deleting.

[vzarytovskii]

@vzarytovskii I simply don't understand why this issue was closed - have you in any way verifed it? I'm constantly experiencing this problem, also on newest VS 17.2.0 Preview 6. Below two merged screenshots: upper before deleting obj/project.asset.json, lower: after deleting.

I explained why I closed it - I was unable to reproduce it on the latest 17.2 and 17.3. on VisualFsharp solution with which I work daily.

I will reopen it since apparently, it needs more investigation. The problem is to get it to reproduce so we can debug it.

[kerams]

VisualFSharp.sln is still broken for me every time (it feels like) I open it without doing a restore with Build.cmd. git clean -xfd did not help.

[vzarytovskii]

VisualFSharp.sln is still broken for me every time (it feels like) I open it without doing a restore with Build.cmd.

This is the problem, I don't see it, I have it currently open and everything seems to be fine (I'm on the latest 17.2 preview).

It's hard to debug something which does not reproduce :(

Do you not run build.cmd whatsoever?

[vzarytovskii]

Building it for the first time with build.cmd is required for tooling to work properly, unfortunately.
cc @KevinRansom

[kerams]

Building it for the first time with build.cmd is required for tooling to work properly, unfortunately.

The first time after cloning/clean, I know, that's not the problem.

My routine:

• open the solution, see that nothing works, close it
• run Build.cmd and once the restore is complete, ctrl-c (I used to let the whole build finish, but it's not necessary - it seems the restore bit is important, which aligns with @daniel-wojcik's findings)
• open the solution again, integration works
• work on some autocompletion fixes, build the VS integration in VS and debug it in an experimental instance
• finish, close the solution, go to bed
• the next day go to step 1

I might have seen this on different solutions, but it must be fairly rare. Also pretty sure I didn't experience this with preview versions of 17.1.

[vzarytovskii]

Building it for the first time with build.cmd is required for tooling to work properly, unfortunately.

The first time after cloning/clean, I know, that's not the problem.

My routine:

• open the solution, see that nothing works, close it
• run Build.cmd and once the restore is complete, ctrl-c (I used to let the whole build finish, but it's not necessary - it seems the restore bit is important, which aligns with @daniel-wojcik's findings)
• open the solution again, integration works
• work on some autocompletion fixes, build the VS integration in VS and debug it in an experimental instance
• finish, close the solution, go to bed
• the next day go to step 1

Hm, I see. I will try to repro with these steps.

Build.cmd is also needed for building the Proto compiler.

Can you try opening compiler service solution and see if anything is different for you? It's in the service directory.