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
Ionide 4.0 roadmap #1108
In dotnet/fsharp#6785 I've talked a bit about upcoming Ionide 4.0. In this issue I'll track main work items that will lead to the release. We will use experimental-fsharp extension to distribute previews. Version 3.X of Ionide is not officially feature-frozen, however it's hard to expect any new huge features in the current state. The work will be happening on 4.0 branch
Just a warning about this decision. I know that at least one of my project can't use .Net Core runtime anymore due to a SO in the F# Compiler.
I think that I have more than one project doing that but I need to check again.
Original issue: #1039
@Krzysztof-Cieslak @baronfel I am not sure if FCS .net core can fully support fsx script on .NET
For sure, i agree that the .NET Core stack should be the default, for best experience for new and existing users, as @cartermp suggested.
.NET Core will be the future, but .NET is important, lot of libs atm.
I think a safer bet is have both stack, but an easier way to choose, not the multiple independent options ( (fsi/fsac/msbuild) we have now who are confusing like
users doesnt care about FSAC/msbuild version. just a bit more the fsi version
Default is .NET Core stack
As a note, the
Another stuff i am thinking can help:
So i think we should threat .fsx and .fs differently.
It doesn't depend on the FSAC runtime, tho - it depends on the project type, and both runtimes support both project types (i.e FSAC netcore can be run against MsBuild 14.0 file that needs to be build with
I think that:
It's not so easy, and we work a lot on that, so i understand is more complicated for users.
But if they choose
Again, the root issue is .NET stack vs .NET Core stack, we should add just an option for that, with a sane default who command the other three (
As a note, VS/rider use .NET stack.
Because is a binary choice, and can vary from script to script, ihmo a config is more work and too hidden when ppl doesnt know about the difference between the two, less so know a config.
Maybe it's better having two commands, something like:
Or we can add a
We can also default FSI based on the current stack (.NET or .NET Core) for the repo
So a more explicit control with a command ihmo is less error prone.
Is not so easy, otherwise all applications where already running on .NET Core only :(
Yes, we need to list and try to minimize differences, that's what everyone is doing, but take time, we are not yet there.
FYI, there's a new extension that provides a GUI for
One issue I have with