Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I get warnings about the FAKE runner being out of date whenever I build and run.
I also get squigglies on the first line of the
build.fsx
file.It looks like the dependencies haven't been updated in a while, so I went ahead and did the updates. I decided to use a dedicated build project instead of using the FAKE runner since this approach seems to be the current best practice.
References:
https://fake.build/guide/getting-started.html#Run-FAKE-using-a-dedicated-build-project
https://stackoverflow.com/questions/66665009/fix-for-package-manager-key-paket-was-not-registered-in-build-fsx/66666479#66666479
Could not find a suitable .NET 6 runtime version matching SDK version: 7.0.100 fsprojects/FAKE#2719 (comment)
I am using the build projects in the following repos as examples:
https://github.com/ionide/ionide-vscode-fsharp
https://github.com/TheAngryByrd/MiniScaffold
The first thing I did was remove the FAKE runner tool using this command:
Then I created a dedicated build project:
I copied the code from the
build.fsx
file into the main function of the dedicated build project and then removed thebuild.fsx
file. I copied the code as-is, so there are no changes to the behaviors. I also replaced thefake.cmd
andfake.sh
files with correspondingbuild.cmd
andbuild.sh
files.This is the old way to invoke the build:
This is the new way to invoke the build:
The
tasks.json
file has been updated to reflect these changes, so you can just press F5 from within VS Code and it works the same as before.I also updated the Paket tool and updated all the packages:
These changes do not affect any of the grammar definitions.