-
-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ionide 4.0 roadmap #1108
Comments
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 |
Same for us, the underlying stackoverflow still isn't solved for some of our projects. |
Yes, I'm aware of the issue - if that won't be fixed when Ionide 4.0 will be ready, we will keep |
@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 FSIAs 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. It's:
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 Again,
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. |
OK, it seems we'll keep |
FYI, there's a new extension that provides a GUI for One issue I have with |
Latest update:
|
|
|
|
|
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
Roadmap:
netcore
runtime of FSAC as default (Update plugin initialization #1114)workspace
method (Update plugin initialization #1114)Update Forge scaffolding to useUse .Net Core Forge templates (Forge core #1113)dotnet new
under the hooddotnet fsi
can't be started on Windows #1087)The text was updated successfully, but these errors were encountered: