Replace ParseFileInProject with ParseFile

[auduchinok]

When dotnet/fsharp#3601 is merged, ParseFileInProject will fallback to ParseFile and generate parsing options on each call.
If ParseFileInProject is going to become deprecated, docs should be updated accordingly.

[dsyme]

This has been done

[goswinr]

@dsyme thanks for all these improvements. The Docs are still out of date no?
http://fsharp.github.io/FSharp.Compiler.Service/editor.html
Shall I open a separate issue for that?

[forki]

Even better: try to directly write something down in PR. ;-) But yes new docs issue is probably good idea Am 04.10.2017 07:30 schrieb "Goswin" <notifications@github.com>:

…

@dsyme <https://github.com/dsyme> thanks for all these improvements. The Docs are still out of date no? http://fsharp.github.io/FSharp.Compiler.Service/editor.html Shall I open a separate issue for that? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#806 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNDu9KXM1hzw8cafDJWfLkmRJh6SLks5soxfhgaJpZM4Pd5_z> .

[goswinr]

@forki I first have to correctly understand the FCS API . Some interesting information seems to be hidden in the open and closed Github issues here.

[forki]

Yes absolutely. And I think we should require docs changes when we accept pull requests that open APIs or change them in the future. Am 04.10.2017 08:24 schrieb "Goswin" <notifications@github.com>:

…

@forki <https://github.com/forki> I first have to correctly understand the FCS API . Some interesting information seems to be hidden in the open and closed Github issues here. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#806 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgND-1BtFZl0IASxBgPFPUdvk0REXNks5soySSgaJpZM4Pd5_z> .

[dsyme]

We just need to republish the docs. I'll do that