Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Experimental version of Ionide #1075
We've decided to publish an experimental version of Ionide as a separate extension.
It will be used for testing important changes that can potentially break users such as moving to new project parser (included in the current experimental version) or moving to LSP protocol for communication with our language server (soon).
We would really appreciate any real-world testing of this experimental extension.
How to try it
You can install it in your vscode, after uninstalling the stable ionide extension, but that's not the easy way because require more work.
For easy testing without breaking your nomal usage, it's recommended to install the experimental version in VSCode Insider version.
So you can have stable ionide on vscode, and experimental in vscode insiders, ready to be used running
VSCode insiders will auto update the experimental extension as usual, ready for new bugfixes.
Any feedback will be really appreciated.
Thanks a lot!
Main changes in current experimental version: project system
Changed the projects parsing and loading of the workspace.
What to test: loading of projects, solution and fsx scripts
It's a big refactoring effort in FSAC and that will allow lots of bugfix and features later (multi target framework support, faster and stable parsing of projects, debug/release configuration, unified .NET and .NET Core FSAC, etc)
Please report issues in https://github.com/fsharp/FsAutoComplete/issues adding
For help installing or report issues, please contact @enricosada
All changelog in the extension release notes, contained also in RELEASE_NOTES_EXPERIMENTAL.md
Hi. Tested experimental with a Fable project and got the following error. (can be reproduced with fable2-samples repo)
When reporting issues on Experimental, should we do it on this issue? or perhaps an Experimental label?