Projects do not seem to be recracked on file changes

[baronfel]

Describe the bug
User @purkhusid on the FSSF slack reported that their projects don't seem to reload after adding a PackageReference element to the project. We should triage this.

To Reproduce
Steps to reproduce the behaviour:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behaviour
The project should be cracked, the new reference should be added, and the ProjectController should be notified of the change.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• OS:
• Ionide version:
• VSCode version:
• dotnet SDK version:
• mono / .Net Framework version:

Additional context
Add any other context about the problem here.

[baronfel]

Context:

Is there any flag that helps with having to reload VS Code every time I add a new NuGet packages to .fsproj ?
_{View in Slack}

[purkhusid]

@baronfel I tested various combinations and the winning combination to get things working was:

1. Add PackageReference to .fsproj
2. dotnet restore
3. Make a change to .fs file and save

My workflow was usually in this order:

1. Add PackageReference to .fsproj
2. Make a change to .fs file and save
3. dotnet restore or dotnet build

Feel free to close the issue if you don't think this is worth checking out!

[baronfel]

That sorta feels to me like we're not triggering a re-parse-and-check of the files in a project when the project is updated.

[TheAngryByrd]

I do have a better project reload in FSAC Adaptive Server now, should I move that code to here or possibly remove the functionality from here?