Update Build.cs #1506
Open
Update Build.cs #1506
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
Nuke.Common.IO.FileSystemTasks does not exist and broke my first time use.
|
I can confirm I had this issue as well and was about to create a PR for the same issue with the same solution, thanks @coendewit |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Nuke.Common.IO.FileSystemTasks does not exist and broke my first time use.
When using the latest version 9.0.4 on macOS, I could not follow the first baby steps: install, setup and run. The setup template referenced a non existent FileSystemTasks. I don't know where it was moved to, but since it is not used in code anyway, I propose to at least remove it.
I confirm that the pull-request: