- Use LSP as communication protocol with FSAC
- Use Dotnet.ProjInfo.Workspace as only way to parse project files
- Use .Net Core version of Forge
workspaceModesetting - we always use FSAC based search to detect projects or solutions in workspace
workspaceLoadersetting - we always use FSAC workspace based project loading.
netcoreby default - recommended way of using Ionide 4.0 is running it on .Net Core. .Net SDK is only strict requirement.
logLanguageServiceRequestsOutputWindowLevelsettings - due to the fact Ionide is really thin layer we now use LSP based logging (hidden setting:
"FSharp.trace.server":"verbose") and additional FSAC logging (
toolsDirPathsetting - it was never used anyway
falseby default - first of all the feature was not working too well (often inserting the repeated namespaces), secondly it caused responsiveness problems (just due to the fact it was huge number of suggestions on even small projects - it turns out there are lot of entities in .Net Framework)
enableBackgroundServicesand set it to
trueby default - there has been huge FSAC refactoring around Background Service that should positively impact Ionide responsiveness (potential cost is RAM usage)
trueby default - as
trueby default, we can enable additional Code Lenses as well.
F#: New Projectcommand now creates F# Core projects
- Improve support for FAKE scripts
- Add FAKE Target outline for FAKE scripts