Enhanced F# Language Features for Visual Studio Code
Part of the Ionide plugin suite. Read detailed documentation at Ionide docs page.
Description
Ionide-VSCode is a VSCode plugin that turns VSCode into a fully-fledged IDE for F# development.
The LSP that powers language features is FSAutoComplete.
The library that powers project and script loading is proj-info
You find a version of this plugin pre-packaged with the FOSS debugger from Samsung here
Requirements
-
.NET 10 runtime - https://dotnet.microsoft.com/download/dotnet/10.0
Ionide runs its language server (FsAutoComplete) on the .NET 10 runtime only, so .NET 8 or .NET 9 on their own are not enough.
The .NET 10 SDK includes this runtime.
-
.NET SDK 8.0 or later, to load your projects - https://dotnet.microsoft.com/download
A global.json can pin the .NET 8 or .NET 9 SDK, and your projects can target net8.0, net9.0 or any other framework.
-
VS Code C# plugin - Ionide’s debugging capabilities rely on either the Omnisharp debugger or netcoredbg.
Features
- Syntax highlighting
- Auto completions
- Error highlighting, error list, and quick fixes based on errors
- Tooltips
- Method parameter hints
- Go to Definition
- Peek Definition
- Find all references
- Highlighting usages
- Rename
- Show symbols in file
- Find symbol in workspace
- Show signature in status bar
- Show signature as CodeLens / LineLens
- Go to MSDN help
- Add
open NAMESPACE for symbol
- Match case generator
- Go to #load reference
- Generate comment for the symbol
- Integration with F# Interactive
- Integration with Forge (Project scaffolding and modification)
- Integration with FSharpLint (additional hints and quick fixes)
- Integration with MSBuild (Build, Rebuild, Clean project)
- Solution / project explorer
- And more…
How to Contribute
This project is hosted on GitHub where you can report issues, participate in discussions, fork
the project and submit pull requests.
Building and Running
See these instructions for setting up your local dev environment.
Guidelines
The Contribution Guide outlines the process and guidelines for getting a patch merged. By making expectations and process explicit, I hope it will make it easier for you to contribute!
Releasing
- Changes collect in the
### Unreleased section at the top of RELEASE_NOTES.md.
- To release, a pull request renames that section to the new version and date (DD.MM.YYYY format please).
- When it is merged into the main branch, the
Release workflow publishes the new version. See the Contribution Guide.
Imposter Syndrome Disclaimer
I want your help. No really, I do.
There might be a little voice inside that tells you you’re not ready; that you need to do one more tutorial, or learn another framework, or write a few more blog posts before you can help me with this project.
I assure you, that’s not the case.
And you don’t just have to write code. You can help out by writing documentation, tests, or even by giving feedback about this work. (And yes, that includes giving feedback about the contribution guidelines.)
Thank you for contributing!
Code of Conduct
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
Copyright
The library is available under MIT license, which allows modification and redistribution for both commercial and non-commercial purposes.
评论