ProjectCracker returns *.fsi files in FSharpProjectOptions.SourceFiles array #812
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…s array (in addition to *.fs files, in right order)
…l ProjectCrackerOptions.Error (new field)
|
I think the problem isn't with the slashes. But somehow, nuget seems to try to access the wrong path. /cc @dsyme, it looks like you broke the build about a month ago with a merge and the Mac/Linux build hasn't completed successfully since. We couldn't readily find the cause, do you have an idea? See also #813.
|
dsyme
approved these changes
Oct 3, 2017
|
Thanks this is great. Sorry it didn't make it into the last FCS release. We have to fix the travis build |
|
Working on it, see #816 |
|
FCS 16.0.2 release |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
...and ProjectCracker throws exception if the Tool returns non null Error.