-
Notifications
You must be signed in to change notification settings - Fork 585
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
What is 5.0 replacement for legacy Fake.FSIHelper.fsiPath? #1841
Comments
I don't think we have one, as we don't have a FSI module on FAKE 5 yet. |
Would that be related to the item Use F# Type Providers and F# Interactive in .NET Core 2.1. (specifically FSI) on the MSFT VS roadmap https://docs.microsoft.com/en-us/visualstudio/productinfo/vs2018-roadmap ? I imagine this is also the major impediment to moving forward with FSharp.Formatting 3.0? |
Maybe a bit, but yeah we probably should upgrade netcore to 2.1 |
Hey @matthid, is this issue do-able? If so, I can port over the fsihelper module. What would the module be called? Fake.FSI.Helper? Or just Fake.FSIHelper? |
@vanceism7 yes I think it can be added. I guess we would name it Fake.DotNet.Fsi or Fake.Tools.Fsi |
PR is welcome. I'm closing this to clean the house a bit ;) |
Just a bump for whoever is wondering, I should have a PR coming in for this pretty soon |
This has been a year, will there be a FAKE 5 FSIhelper module, or is this still open? |
Yes it is here since 5.1.0, should have liked those issues up :) |
Description
What is 5.0 replacement for legacy Fake.FSIHelper.fsiPath?
Actual behavior
No migration help message available.
Related information
5.0.0-beta025 +
The text was updated successfully, but these errors were encountered: