This moves the build scripts away from using fake-cli and using a dotnet project to run it. fake-cli hasn't been updated in quite a long time and isn't using the latest version of FSharp.Compiler.Services so tooling like Ionide work with it anymore.
There aren't major changes to the build script other than configuring it to run in just a dotnet process. The big differences are:
What types of changes does your code introduce to MiniScaffold?
Put an x in the boxes that apply
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
[ ] Build and tests pass locally
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have added necessary documentation (if appropriate)
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Proposed Changes
This moves the build scripts away from using
fake-cliand using a dotnet project to run it.fake-clihasn't been updated in quite a long time and isn't using the latest version of FSharp.Compiler.Services so tooling like Ionide work with it anymore.There aren't major changes to the build script other than configuring it to run in just a dotnet process. The big differences are:
These should help anyone looking to migrate their code to use a dotnet project.
Summary
build.fsxto a.fsprojunder./build/which is largely similar.Deals with https://github.com/TheAngryByrd/MiniScaffold/issues/231 a bit
Types of changes
What types of changes does your code introduce to MiniScaffold? Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...