Remove dependence on runfsc.cmd and runfsc.sh #5882
Merged
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.
The dotnet cli uses RunFsc.cmd and RunFsc.sh to execute the FSharp command in the build task using a single command.
There is an issue with this on those rare Linux packagings that don't have a bash shell configured.
This change, modifies the way the fsharp build task executes the fsharp compiler.
We now use the DotnetFscCompilerPath property to be the path to the F# compiler executable.
FscToolPath and FSCToolExe now point to the dotnet.exe specified in the guaranteed global property DOTNET_HOST_PATH.
What's nice about this, is that no sdk changes are necessary.