Fix F# targets on xbuild 12.0 & 14.0 #541
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.
On xbuild the
MSBuildExtensionsPathproperty is multi-valued. However, this only works inImports. When used in a property, it has a single value - which is not where the F# targets are installed on Mac.As as result, the Xamarin targets were falling back to checking
MSBuildBinPath, however the F# targets were only installed into the bin path of the 4.0 toolset, and so this failed with the 12.0 and 14.0 toolsets.Also, make the locations we check for F# consistent across all the targets (maybe it should be factored out).